[NoMongo] Self Signed SSL Certificates Causing Issues with Caddy

[vasujain275]

Describe the bug
The development server is currently configured to use self-signed certificates for HTTPS in our Express GraphQL API. This is causing issues when hosting on a cloud VPS with a reverse proxy (Caddy) configured. The development server should use HTTP only, leaving HTTPS to be handled by Caddy in the production environment.

This issue is blocking progress on hosting the API on the cloud VPS (related to issue #1428).

To Reproduce
Steps to reproduce the behavior:

1. Set up the talawa api on your local dev.
2. Attempt to access the API via HTTPS, it will show warning that this site is using unserucred certificates for https.

Expected behavior
The talawa api should be acceed by http only in the local envirment which can be converted to https using caddy in production.

Actual behavior
The self-signed certificates from the development server conflict with the reverse proxy (Caddy) configuration, leading to errors when accessing the API via HTTPS on the cloud VPS.

Screenshots

Additional details
This issue is a blocker for issue #1428. Resolving this would allow the development server to run on HTTP only, and Caddy to handle HTTPS in production, enabling smooth deployment to the cloud VPS.

[palisadoes]

@xoldd This may be something to investigate

[xoldd]

In develop-postgres branch the node.js server for talawa api runs only on http. For accessing it over https in all environments the self signed certificates are generated and managed internally by the caddy docker container when it detects that the value of CADDY_TALAWA_API_DOMAIN environment variable is localhost. It is a feature provided by caddy for easily testing if the application is working properly over https in development environment as well.

[vasujain275]

@xoldd but the issue is with devlop branch, it is using openssl generated self signed certificates for the node http server.

[xoldd]

Then you'll have to get rid of it I guess? Idk what else could be done.

[palisadoes]

@vasujain275 have you found a solution for disabling HTTPS?

[PurnenduMIshra129th]

@palisadoes please assign i will try to do it. If no one is assigned

[Cioppolo14]

@PurnenduMIshra129th Right now you have 2 issues already, let me know if one issue is completed, and I can assign you.

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

[prayanshchh]

can i try this?

[PurnenduMIshra129th]

@Cioppolo14 ok i understand

[IITI-tushar]

@Cioppolo14 can i take this??please assign...

[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.

[Cioppolo14]

Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue.

[IITI-tushar]

assign me again please @Cioppolo14

[IITI-tushar]

@vasujain275 @xoldd
Here,
https is only for production and development is using http only...

[IITI-tushar]

@vasujain275 can you provide more info on how to reproduce this??

[PurnenduMIshra129th]

@IITI-tushar did you find any solution?

[IITI-tushar]

@PurnenduMIshra129th are you able to reproduce it??

[PurnenduMIshra129th]

No i am not working on this issue .

[palisadoes]

Is this still valid?

[palisadoes]

Closing.