New user here and love the product!
I have spent 2 days fighting this problem and am finally asking for help, so not a totally newbie question (even though this question has been asked before and answered in various forms).
I was trying to host a docker compose based install on the Digital Ocean droplet that already had ports 80 and 443 occupied.
I tried so many things which I will get into later.
For now (and for easier debugging or offering help), here is the set of simplified steps I have taken to reproduce the issue
- A brand new docker compose based appsmith install with two changes in the docker-compose.yml
ports: - "8080:80" - "8443:443" - "9001:9001"
Started appsmith and it is working great on port 80 over http
However, going to port 8443 over https gets a connection refused
To minimize the impact of browsers etc, I finally went old school telnet to ports 8080 and 8443 and here are the results
Works well and is served by the Appsmith nginx
However on Port 8443
(Sorry - new posters are only allowed one image so I had could only use one screenshot)
- The question is that for a default install, is nginx listening on 443?
- Does it use a self-signed cert if the APPSMITH_CUSTOM_DOMAIN has not been configured? to get started up? Or does it just reject anything on that port?
I tried to poke around the nginx conf file on github but couldnt find this clearly.
Now, I have already tried all options of ports, forwarding, custom domains etc and nothing has worked for 2 days.
So I tried to simplify this with going direct to the machine and doing everything using basic command on the localhost to eliminate firewalls, dns entries etc
Any help/pointers would be greatly appreciated.
My final goal is to run appsmith on a digital ocean droplet which already has another docker stack using 80/443 using caddy.
(I went down the caddy forward 80/443 route to appsmith using a domain name first, when that didnt work I resorted to isolating the problem and finally hit the connection rejected outright by appsmith on the https port)