Hey All,
I recently installed the software appliance 9.201-25 on my custom hardware for home. I did a fresh install because I was running into an Up2Date issue where it could not recognize there were updates. I am not 100% sure this will fix the problem, but it doesn't hurt. That said, I ran into an interesting bug that I can't quite figure out. Perhaps someone who has come across this before/has more expertise could identify the source problem.
Background info:
1. This machine and the host involved were working flawlessly on the network together on 9.201-23. No configuration or hardware was changed since upgrade. So no configuration issues and no hardware compatibility issues.
2. Running latest versions of Firefox / Google Chrome. Attempted to access web admin with both.
3. Attempting to connect to WebAdmin with https://(ip address):4444
Relevant machine hardware/software information:
1. Server: Supermicro Atom Server board, two intel NICs.
2. Host: Windows 8.1 pro, intel NIC.
The problem:
1. I was unable to access the web admin after the fresh installation, which I did twice, just to make sure.
Symptoms:
1. For some reason the web browsers just display "unable to connect" messages.
2. A ping of the server's ip showed 100% packet loss and "general failure".
3. As root, running 'ifconfig eth0' it showed packets being received.
4. I navigated to the 'packetfilter.log' file in the log directory and found something interesting. The firewall was blocking the webadmin connection attempts using firewall rule 60001. It also showed the the destination port was "443". Even though I attempted many times to connect using port 4444. It almost seems like using the 'https://' prefix caused the attempt to route to the SSL port rather than the custom port. This is very strange because I have had no issues with this previously. It leads me to believe there is an issue with the default UTM 9.201-25 software configuration itself.
The resolution:
1. I used the command steps 'cc' -> 'webadmin' -> 'port@' -> '=443' to change the port to 443. That did the trick!
----------------
A few side notes about the installation for newer users:
1. Don't use pen drive linux software to attempt to write the ISO to a usb key. It corrupts the 'install.tar' file and says it is not found, even though I watched it "write" to the usb drive in the logs.
1.a. The 'dd' command on linux might work in this context, but I haven't tried it. They don't call it "data destroyer" for nothing...
1.b. Install this from a optical disk if possible.
This thread was automatically locked due to age.