Skatman Posted May 15, 2021 Share Posted May 15, 2021 (edited) As per the title. I had my server up and running for ages. probably around a year or so. Shut everything down to perform some maintenance on the server (hoover dust out and install 2 new HDDs). Anyway, on boot I can't connect to the GUI and been waiting a while. Nothing has changed other than the addition of two more drives. USB still in the same slot and still formatted in the same way. I can ping it from my core firewall, the CLI is up when connected directly via a monitor. Checked the IF config and there's no IP address in the eth0 section, but the correct IP is stated in the br0 section and at the login screen. Traffic is being allowed via the core firewall. Tried accessing it via both HTTPS and HTTP. Error code is "Refused to Connect", which says to me that it is reaching the server, but the server doesn't like it. Going to be difficult for me to pull any config logs as I don't have SSH enabled. Best, Edited May 15, 2021 by Skatman 1. Added Connection Error. 2. Marked as Solved. Quote Link to comment
Skatman Posted May 15, 2021 Author Share Posted May 15, 2021 Just checked the 'df' command and can see that /boot is mounted to /dev/sda1 (or the other way around - forget which). Quote Link to comment
Skatman Posted May 15, 2021 Author Share Posted May 15, 2021 Turned out the NTP Server portion of my Core Firewall (NGFW) had a fit after updating and decided to change the date to 2012. This caused the webproxy function to fail resulting random browsing failures. Really odd. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.