API: Fix Docker in the develop branch for API and Admin

[palisadoes]

This is for the Develop Branch

Describe the bug

1. In the develop branch we cannot get the API docker instance to communicate with the Admin instance.
2. We need the following:
   1. The API instance must only communicate on port 4000, not 80 or 443. It must be able to respond to queries from the Admin instance on port 4000
   2. The Admin instance must only communicate on port 4321, not 80 or 443. It must communicate with the API on port 4000
3. The queries in the develop branch for logging in seem to be malfunctioning. You may need to eventually try with code from an older PR

To Reproduce
Steps to reproduce the behavior:

1. Run the API as a docker instance
2. Run Admin as a docker instance
3. There is no communication

Expected behavior

• It works

Actual behavior

It doesn't work. These are the symptoms

1. When the nginx configuration is removed from the API docker files, we can communicate with it easily. This query succeeds:

   curl -X POST "http://HOSTNAME:4000/graphql" \
   -H "Content-Type: application/json" \
   -d '{"query": "{organizations {name}}"}'
   

2. You can communicate with the Admin instance on 4321 without issue from an external machine

   telnet ADMIN-HOST 4321
   

3. You can communicate with the API instance on 4321 without issue from an external machine

   telnet API-HOST 4321
   

4. When Admin tries to communicate with the API we get:
   1. 404 errors
   2. No traffic between the API and Admin docker containers
5. On the API
   1. No traffic between the API and Admin docker containers
   docker logs -f talawa-api-dev
   1. TCP dump on port 4000 doesn't show traffic
   tcpdump -n -X tcp port 4000
   1. On Admin
   1. Developer tools > network, shows traffic not being routed correctly

Screenshots

• N/A

Additional details

Please collaborate as a team on these 2 issues

1. API: Fix Docker in the develop branch for API and Admin #3199
2. Admin: Fix Docker in the develop branch for API and Admin talawa-admin#3583

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[VanshikaSabharwal]

please assign

[prayanshchh]

I can work on this with @VanshikaSabharwal, if u want I can unassign from my existing issues as they aren't high priority

[CHIRANTH-24]

@palisadoes I would also like to work on this with @VanshikaSabharwal and @prayanshchh .

If you could verify my other issue and unassign me

[VanshikaSabharwal]

Yes @prayanshchh @CHIRANTH-24 we can connect on slack. I am working on the issue.

[prayanshchh]

Yes @prayanshchh @CHIRANTH-24 we can connect on slack. I am working on the issue.

i have slacked you the problems in docker for admin

[harshdev2909]

Hi @palisadoes @VanshikaSabharwal , I'd like to work on this issue and investigate further. I will start by examining the Docker networking setup and the interaction between the API and Admin instances, particularly focusing on the port configuration (4000 for the API and 4321 for Admin) and the Nginx setup. I'll also check for potential issues with the current login queries in the develop branch and look into any relevant changes from older PRs that may resolve the malfunctioning behavior.

Please assign me to this issue when possible. Thank you!

[CHIRANTH-24]

Hi @prayanshchh and @harshdev2909
Are you able to run both the containers?

[VanshikaSabharwal]

@harshdev2909 if you are successful then you will be assigned but right now i am already working on it. It's not as easy as it looks

[prayanshchh]

Hi @prayanshchh and @harshdev2909 Are you able to run both the containers?

api is working as exepected, admin isn't

[CHIRANTH-24]

Hi @prayanshchh and @harshdev2909 Are you able to run both the containers?

api is working as exepected, admin isn't

Not able to access the admin portal at 4321?

[prayanshchh]

Hi @prayanshchh and @harshdev2909 Are you able to run both the containers?

api is working as exepected, admin isn't

Not able to access the admin portal at 4321?

this is what I get, this is what the issue is about

[CHIRANTH-24]

Hi @prayanshchh and @harshdev2909 Are you able to run both the containers?

api is working as exepected, admin isn't

Not able to access the admin portal at 4321?

this is what I get, this is what the issue is about

Yes
If we clear the localstorage we will be able to see the login screen

But the api port is not able to communicate with the admin

[palisadoes]

@VanshikaSabharwal There has been significant progress. This issue may have to be closed.

• API: Extremely Poor Docker Resource Utilization Efficiency #2730 (comment)

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

Closing. This works