[Bug]: 502 BAD Gateway is shown when running NGINX with Appsmith's staging server hosted at https://release.app.appsmith.com

Harshithazemoso commented 3 months ago

Is there an existing issue for this?

[X] I have searched the existing issues

Description

I am trying to set up Appsmith locally. I followed the steps provided in the Clientsetup.md, and the application works fine when running with the local frontend and backend setup. However, an issue occurs when I run sudo ./start-https.sh https://release.app.appsmith.com followed by the yarn start command. After the page loads, it stops and returns a 502 Bad Gateway error.

Can you please assist in resolving this issue?

Steps To Reproduce

1.Move to the app/client directory 2.Run yarn install command 3.Run sudo ./start-https.sh https://release.app.appsmith.com [should show that NGINX STARTED] 4.Run 'yarn start and when we redirect to thehttp://dev.appsmith.com` we could see that 502 bad gateway at the top or in the Network tab in the dev tools .

Public Sample App

No response

Environment

Production

Severity

Medium (Frustrating UX)

Issue video log

No response

Version

Release v1.26

github-actions[bot] commented 3 months ago

We have found issues that are potential duplicates:

[#33999] [Bug]: 502 BAD Gateway is shown when running CADDY with Appsmith's staging server hosted at https://release.app.appsmith.com (95%) If any of the issues listed above are a duplicate, please consider closing this issue & upvoting the original one.
Alternatively, if neither of the listed issues addresses your feature/bug, keep this issue open.

akshayvijayjain commented 3 months ago

This one is intermittent issue, it is existing for some users and not for others, we are not able to figure out the cause of the issue

@Nikhil-Nandagopal

Request you to direct it someone who can offer some insights and direction, so our team work can based on direction.

AnkitaGupta111 commented 3 months ago

Facing the same issue. Recorded a video for the same by following steps mentioned in description.

https://github.com/appsmithorg/appsmith/assets/51366428/e67719d0-dec5-4786-aa5d-34e81eeb1c99

Also ran yarn start after nginx started

akshayvijayjain commented 3 months ago

@AnkitaGupta111 @Harshithazemoso @Nikhil-Nandagopal I noticed logs mentioned nginx being used from docker.

so I installed nginx as a service using ubuntu's apt package manager. using steps in this link https://phoenixnap.com/kb/nginx-reverse-proxy#ftoc-heading-3

and was able to start the frontend with release backend.

I was facing 502 bad gateway also with local backend setup with using nginx from docker, now that is also running properly by using system nginx service.

sudo apt update
sudo apt install nginx
sudo systemctl start nginx
sudo systemctl enable nginx
sudo unlink /etc/nginx/sites-enabled/default

started frontend client using yarn start inside app/client folder started nginx with following command sudo ./start-https.sh https://release.app.appsmith.com

killed other process on port 80 , when asked in the prompt by start-https.sh

akshayvijayjain commented 3 months ago

I had already logged in appsmith on app.appsmith.com with my email credentials,

when I entered those using my local frontend and release backend, it mentioned that credentials were wrong when i went to reset password page, it showed screen, that I need to setup email service, to be able to receive reset password link https://docs.appsmith.com/getting-started/setup/instance-configuration/email#configure-email

so I logged in using google oauth, but then I am not able to logout Screencast from 09-06-24 11:01:31 AM IST.webm

akshayvijayjain commented 3 months ago

As I was able to start with local nginx service, that means

we have to update the nginx conf, so that it works for docker 's nginx
we have to update the readme to mention that installing nginx service is pre-requisite

appsmithorg / appsmith