Open Harshithazemoso opened 3 months ago
github-actions[bot]
commented
3 months ago We have found issues that are potential duplicates:
akshayvijayjain
commented
3 months ago Another related error, I am not seeing bad gateway,
I am getting bad gateway in response of view.
Note the "X-Request-Id: invalid_request_Id" in response header
akshayvijayjain
commented
3 months ago surprisingly I am able to run local frontend with release backend using command
sudo ./start-caddy.sh https://release.app.appsmith.com
I have not done any special setup apart from installing nginx, about which I mentioned in its relevant ticket. https://github.com/appsmithorg/appsmith/issues/33997
Nikhil-Nandagopal
commented
2 months ago Bumping this issue up to prod because it should have made it's way there by now if it was not fixed
Is there an existing issue for this?
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-caddy.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.
Steps To Reproduce
1.Move to the app/client directory 2.Run yarn install command 3.Run sudo ./start-caddy.sh https://release.app.appsmith.com [should show that CADDY 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
Release
Severity
Medium (Frustrating UX)
Issue video log
No response
Version
Release v1.26