…telecommuting from the twilight zone. it’s not that far. i’m in the same room as the devices.
.-/+oossssoo+/-. [email protected]
`:+ssssssssssssssssss+:` -------------------
-+ssssssssssssssssssyyssss+- OS: Ubuntu 24.04.3 LTS x86_64
.ossssssssssssssssssdMMMNysssso. Host: 7033A2U ThinkCentre M91p
/ssssssssssshdmmNNmmyNMMMMhssssss/ Kernel: 6.14.0-33-generic
+ssssssssshmydMMMMMMMNddddyssssssss+ Uptime: 2 hours, 32 mins
/sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Packages: 3123 (dpkg), 11 (snap)
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Shell: bash 5.2.21
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ Resolution: 1920x1200
ossyNMMMNyMMhsssssssssssssshmmmhssssssso DE: GNOME 46.0
ossyNMMMNyMMhsssssssssssssshmmmhssssssso WM: Mutter
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ WM Theme: Yaru-cinnamon-dark
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Theme: Yaru-blue [GTK2/3]
/sssssssshNMMMyhhyyyyhdNMMMNhssssssss/ Icons: Yaru-blue [GTK2/3]
+sssssssssdmydMMMMMMMMddddyssssssss+ Terminal: gnome-terminal
/ssssssssssshdmNNNNmyNMMMMhssssss/ CPU: Intel i5-2400 (4) @ 3.400GHz
.ossssssssssssssssssdMMMNysssso. GPU: Intel 2nd Generation Core Processor Family
-+sssssssssssssssssyyyssss+- Memory: 3465MiB / 7768MiB
`:+ssssssssssssssssss+:`
.-/+oossssoo+/-.
Hey all,
I’m running an Apache-free Hestia setup — just Nginx and PHP-FPM — and after reconfiguring my home network (Ethernet/Wi-Fi/LAN changes), I’ve run into a few issues.
Main problem:
NGINX refuses to restart, even after I’ve disabled or suspended all sites.
I’m fairly comfortable with traditional /etc/nginx/ setups but still learning how Hestia structures things. Could someone point me to the preferred configuration and log locations for Nginx within Hestia? I want to see what’s actually failing before I go breaking more things.
Possible cause
After the network changes, I noticed my sites under Hestia.HOST became unreachable. I suspect I confused Hestia’s DNS or IP mapping.
Here’s what I did:
-
In the DNS tab, I set the IP to match the one shown in the Web tab for the site.
-
It “kind of” works either way, but I’m not sure if that’s correct practice.
So:
-
Should Hestia’s site configs use
127.0.0.1, a private LAN IP (e.g.192.168.x.x), or my public IP? -
And if I manually edit DNS records to match Web settings, is that actually required — or could it break Nginx restarts?
Context
I’ve been switching between wired and wireless connections — currently the Ethernet port’s tied up by the TV — and I’m using T-Mobile 5G Home Internet (which can be… temperamental).
Also, full disclosure: I’m recovering from a brain injury, so if I phrase things oddly, I appreciate your patience. The goal’s just to get my setup stable again.
Any insight, examples, or references to proper Hestia docs would be greatly appreciated.
Thanks in advance,
Jeff (@ajaxStardust)