#Error 503 on Client side, even with self-hosted Server side running
1 messages · Page 1 of 1 (latest)
Now, I tried to run the start-https.sh with: ./start-https.sh https://localhost:8080. Also no results.
Hi there!
Are you having issues setting up appsmith locally?
Yes. Disregarding the changes mentioned above, I've followed all the steps in the instructions in the "Clientside.md" and "Serverside.md" files, but they seem to be unable to see each other.
Okay.
Can you try to run the client side only and use the staging api just to see if
it works for you.
You can do this with ./start-https.sh https://release.app.appsmith.com
https://github.com/appsmithorg/appsmith/blob/release/contributions/ClientSetup.md#if-you-would-like-to-hit-a-different-a…
See the url above for reference
Doing exactily as the steps mentioned, the same error 503 ocurred. 😢
Please send us the server logs to help us investigate the issue. You can grab
the logs by running docker logs -f appsmith.
Or you could follow the steps from this guide on how to get the
logs
Here it is. I've also added mongodb and redis logs
Thanks for that. Could you try re-cloning the repo and trying the steps again
from scratch?
Re-cloned, followed the steps from Clientsetup.md and the video, still nothing.
Ok. Could you provide a screen recording of your setup process, as well as the
full logs from trying to start the client?
Here's the recording. Can you tell me how can I get the logs you're referrering to?
I'm not able to open the mkv file. Hello! You can grab the logs by running
docker logs -f appsmith.
Or you could follow the steps from this guide on how to get the logs:
https://docs.appsmith.com/learning-and-resources/how-to-guides/how-to-get-container-logs