Can't connect to my main cloudron webpage
-
@aestela the domain is for sale even. Can you check if the domain has not expired?
-
@aestela said in Can't connect to my main cloudron webpage:
I am able to ssh using Putty. Yes I mean I can't connect through the web browser my.axiomtechnolgies.io
Ah, there is a typo here. I guess you meant
my.axiomtechnologies.io
(missing o). -
@aestela Indeed that domain is all and well. We were working of an incorrect domain
Can you SSH into the server and check
systemctl status box
andsystemctl status nginx
? It looks like nginx is not running.I also replied from support. If you give us SSH access, we can look into this as well.
-
Yes, that's the correct domain my.axiomtechnologies.io. Any idea why it doesn't load the webpage you can check all the DNS records they look good to me I don't get any errors other than http://axiomtechnologies.io not loading. https://mxtoolbox.com/emailhealth/axiomtechnologies.io/
-
@girish May 24 08:41:53 Axiom-Techs-Svr sudo[30605]: p
systemctl status nginx result:
root@Axiom-Techs-Svr:~# systemctl status nginx
β nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset:>
Drop-In: /etc/systemd/system/nginx.service.d
ββcloudron.conf
Active: active (running) since Wed 2023-05-24 07:33:29 UTC; 1h 47min ago
Docs: man:nginx(8)
Main PID: 5888 (nginx)
Tasks: 9 (limit: 18648)
Memory: 26.5M
CGroup: /system.slice/nginx.service
ββ 5888 nginx: master process /usr/sbin/nginx -g daemon on; master>
ββ30609 nginx: worker process
ββ30610 nginx: worker process
ββ30611 nginx: worker process
ββ30612 nginx: worker process
ββ30613 nginx: worker process
ββ30614 nginx: worker process
ββ30615 nginx: worker process
ββ30616 nginx: worker processMay 24 07:32:13 Axiom-Techs-Svr nginx[776]: nginx: [warn] "ssl_stapling" ignore>
May 24 07:32:23 Axiom-Techs-Svr nginx[776]: nginx: [warn] "ssl_stapling" ignore>
May 24 07:32:33 Axiom-Techs-Svr nginx[776]: nginx: [warn] "ssl_stapling" ignore>
lines 1-23 -
@aestela OK, interesting. nginx is running. Is there a firewall by any chance in front of this server?
-
@aestela You must also add port 80 and port 443 to the inbound permitted ports list (along with port 22). These 2 ports are HTTP and HTTPS respectively.
(Was this something new ? How was it working before without allowing these ports?)
-
A more complete list is here - https://docs.cloudron.io/security/#inbound-ports (depending on what features you use).
-
@aestela said in Can't connect to my main cloudron webpage:
By the way is there any way to improve my reputation it keeps making me wait 360 seconds?
I gave you some upvotes, should be ok now, I think.
-
root@Axiom-Techs-Svr:~# cloudron-support --enable-ssh
Enabling ssh access for the Cloudron support team...Done
It looks like ssh is enabled if you want to check the server. It was working before without the inbound rules 80 and 443. I just added the inbound rules -
@aestela It works now already after you added the inbound rules. Maybe something changed in Hetzner side?
-
-