Little confused - is 24.11 not available for SG-1100? Says at latest revision 24.03 RELEASE
-
Hmm so it did appear to upgrade to 24.03 patch 1?
You might have a filesystem issue that cannot be fixed by the normal processes that run at boot. It's also possible you have an issue with the eMMC drive.
Try checking the eMMC status: https://docs.netgate.com/pfsense/en/latest/troubleshooting/disk-lifetime.html#emmc
If that looks OK then I'd try backing up the config and re-installing 24.11 clean: https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html
-
@stephenw10 Tried checking the eMMC status (and it displayed a lot if information), but it appears my unit doesn't support the EOL information. No output when I tried that last command (the one with egrep) and scanning the output manually shows nothing regarding EOL.
-
@stephenw10 So, I decided to fire up my spare SG-1100 (let's call it device B) and update it and get it working before messing any further with the original SG-1100 that is stuck on 24.03, but functions fully. Let's call the original, on 24.03, device A.
On device B (again, the spare) I went ahead and did a full reinstall to 24.11. Before doing so, I made a config backup from device A. After I reinstalled pfSense on device B, I restored the configuration file.
Seems to be running perfectly, everything works fine except one thing. My Nextcloud server cannot be found via my custom domain. The Nextcloud server is online, with the static IP I have assigned in pfSense, and it can browse the internet. If I connect directly to itself in the browser (i.e. 192.168.2.252) the Apache "Success!" page displays, meaning the Nextcoud server is up and running. But I cannot get to it (the application) from any device.
If I plug device A back in, everything comes up and is accessible including the Nextcloud server.
I have combed through the NAT settings (I'm using port forwarding) for the OPT port (where the Nextcloud server is plugged into) but I can't see anything that is out of whack. I also checked and the NAT reflection is set up correctly. So I'm not seeing any differences between the setup of the two devices. I don't expect to, since I restored the same configuration into device B that came this morning from device A.
Is there anything significantly between 24.03 and 24.11 as far as the configuration that would cause this issue?
I know the topis has shifted here. But I'd really like to get this device B fully functional and then go back and reinstall on device A.
-
Hmm, nothing significant changed between 24.03 and 24.11.
https://docs.netgate.com/pfsense/en/latest/releases/24-11.html#new-features-and-changesSo clients are resolving your nextcloud server to the external address?
Check the states when you try to connect to it. You should see two NAT states created if reflection is working correctly.
-
@stephenw10 I'm seeing a bunch of States listed. Here's a few (filtered for OPT, since that's the interface where the Nextcloud server is plugged into. It's the only device on that interface):
192.168.2.252 is the IP of the Nextcloud server. I checked my domain provider settings and the IP address I have configured is unchanged and matches my WAN address.
I'm currently on a laptop at 192.168.1.150 and I can get to the Apache "Success" page by hitting 192.168.2.252 on the browser on this machine.
I refreshed the States list and I do see two states at the bottom which appear to tie the 192.168.2.252 address to the WAN address. Both have this status:
Refreshed again and I see 3 now tying the two together, status SINGLE:MULTIPLE -
@stephenw10 So I went in and did a Certbot renewal dry run on my NC server. The dry run ran successfully. I did it twice to confirm.
That tells me that port 80 is accessible. So maybe something is wrong with how I have port 443 forwarded?
FIlter rule:
-
@stephenw10 Update: it's working now. Tested on multiple devices
Appreciate you help and assistance, as always.
Tomorrow I'll try a clean install on my original device and see if that works. I have a feeling it's hardware-failing, since it restarted several times early this AM.
-
Any idea what was failing? I would have expected that to 'just work'.
-
@stephenw10 Well I have to admit that I overlooked something very simple and elemental. My ISP decided to change my cable modem's IP right when I started struggling with this issue. I checked yesterday and it was set at the address I've had for a long time. It was working this morning too before I started reinstalling on the backup device. I double checked this morning after reinstalling on the other device and was surprised to see that it had changed. I updated it in my domain's DNS settings and slowly tjings started to get back to normal.
So user error was the cause of NC not being reachable. Hangs head in shame
-
Aha, that would do it! Easy mistake, we've all done stuff like that.
-
G Gertjan referenced this topic on
