-
First, I ran it on a server within my LAN, but at the end of the installation, it said "Congratulations! Your Coolify instance is ready to use. Please visit http://[My public IP4 address]:3000 to get started.", which was inaccessible. At first I thought it was not successfully installed. After a bit of trying, I figured out that the correct address was http://[the computer's NAT IP4 address]:3000. Now, I added a new application with the git source https://github.com/coollabsio/nodejs-example/tree/main. In the URL (FQDN), I wrote something like "http://test1.servername.lan". In my home router's DNS setting, I had set "*.servername.lan" or "*.servername" would be the servers NAT IP4 address. So, on any computer within my LAN, typing "ping test1.servername.lan" will show the server's IP4 address. When I deployed it and clicked "Open", the web browser said "Server not found". What is the problem? In the Build tab, it all says the deployment was successful. In the Application Logs,
How can I find the reason? I tried to edit "Exposed Port", but that field seems read-only. FireFox says "Server not found", but Edge says "test1.servername.lan refused to connect". It is Ubuntu server 22.04, and firewall is not installed. Anyway, how does Coolify listen to the incoming connection to deployed projects? I saw the list of ports using |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Eh. Clicking Dashboard -> Destinations -> Local Docker -> Force restart proxy made it work. Why doesn't it automatically start? Before doing this I had tried restarting the server (not Coolify, but Ubuntu) and even that did not fix it. Also, when creating a new application (using sample github projects in the doc) randomly the application state is "running" and I cannot enter the URL (FQDN). There is no stop button yet, so the only workaround I could find was refreshing the page. Is this product alpha version or something? |
Beta Was this translation helpful? Give feedback.
Eh. Clicking Dashboard -> Destinations -> Local Docker -> Force restart proxy made it work. Why doesn't it automatically start? Before doing this I had tried restarting the server (not Coolify, but Ubuntu) and even that did not fix it.
Also, when creating a new application (using sample github projects in the doc) randomly the application state is "running" and I cannot enter the URL (FQDN). There is no stop button yet, so the only workaround I could find was refreshing the page.
Is this product alpha version or something?