[Bug]: issue: after running Appsmith client locally(dev.appsmith.com) it's showing that "Your connection is not private", how to resolve it please help?

[deepakk0109]

Is there an existing issue for this?

• [X] I have searched the existing issues

Description

after running Appsmith client locally(dev.appsmith.com) it's showing that "Your connection is not private", how to resolve it please help?

Steps To Reproduce

I followed each step in WSL: https://github.com/appsmithorg/appsmith/blob/release/contributions/ClientSetup.md

Public Sample App

No response

Environment

Production

Severity

High (Blocker to building or releasing)

Issue video log

No response

Version

Self hosted v1.41.0

[ALOK9442]

hey @deepakk0109 just type "thisisunsafe" while you are on this page it will take you to the dev.appsmith.com I do not have the correct explaination but what i noticed is, it is because of the chrome and the system security issue which led to this issue of not opening a local https server

[deepakk0109]

After typing "thisisunsafe" I got "502 Bad Gateway", what could be the possible reason?

I followed these steps for running the application: (https://github.com/appsmithorg/appsmith/blob/release/contributions/ClientSetup.md) @ALOK9442

[ALOK9442]

Hey @deepakk0109 the reason why you are getting 502 bad gateway is that the client side isn't connected to server, make sure you run the command "sudo ./start-https.sh https://release.app.appsmith.com" before starting the server each as it connects it to the backend services and then start the frontend, also check if you are mapping the dev.appsmith.com domain in the file hosts in windows (I would suggest use wsl or ubuntu)

[deepakk0109]

Hey @ALOK9442 it works, and I am using local server(http://localhost:8080/) and getting following error on (dev.appsmith.com) while going for application building(editing page), how to resolve it? Error: RTS server error while processing request: Error fetching latest DSL version

[ALOK9442]

hey @deepakk0109 I never did the setup of server side locally, so could not help with it but this issue never arises for me as I was using the backend service from their web only