After update to 2.7.1, Bad Gateway: Nginx
-
Updated and web-ui started to fail with "Bad Gateway" Nginx error. Made a clean install with 2.7.1 and same problem. Reinstalling 2.7.0 solved the problem. Intel NUC with a USB dongle. Very basic setup. Nothing extra configured. Has anyone had similar things happening? What might cause it?
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
@Kartsa79 That error typically shows up if the web server can't connect to an internal/back end process. For instance an actual public web server may have nginx in front of Apache, and the error shows when Apache is not running.
Could the USB not be detected in 2.7.1? Does the console show it?
-
Any errors shown in the system log?
If you can't access it in the gui you can run
cat /var/log/system.logat the CLI. -
I reinstalled pfsense to the computer, but changed the usb-dongle from wan to lan. Now it seems to work. Yesterday when I was havin problems with pfsense, I tried to install IPFire instead. That also had a problem with DNS-servers. Could not to make it work at all. USB dongle was also the wan then. I did not look any logs yesterday, just went and installed IPFire. I guess the problem is the USB ethernet dongle. Funny, but it worked with pfsense 2.7.0. I also used it with OpenWRT and rpi4 for about six months with no problem. It is Asix based dongle. I also happen to have realtek chip based dongle and it stopped working also with pfsense 2.7.1. Now I am getting full 200MBs download but only really low upload speeds. Could be the Ookla tests fault too. I need to try it later. But yeah, I guess that dual NIC mini PC could be the answer. Those dongles seem to be bit variable in reliability. Also I noticed today that the LAN lost link for a moment after the speed test. So yeah, dual NIC pc... Minis Forum GK41 looks intersting
-
@stephenw10 In /var/log/system.log lots of this:
ov 20 20:51:54 pfSense kernel: ue0: link state changed to UP
Nov 20 20:51:54 pfSense check_reload_status[437]: Linkup starting ue0
Nov 20 20:51:54 pfSense kernel: ue0: 2 link states coalesced
Nov 20 20:51:54 pfSense kernel: ue0: link state changed to UP
Nov 20 20:51:54 pfSense check_reload_status[437]: Linkup starting ue0
Nov 20 20:51:54 pfSense kernel: ue0: 2 link states coalesced
Nov 20 20:51:54 pfSense kernel: ue0: link state changed to UP
Nov 20 20:51:54 pfSense check_reload_status[437]: Linkup starting ue0
Nov 20 20:51:54 pfSense kernel: ue0: 2 link states coalescedAnd later:
20:51:58 pfSense php-fpm[13827]: /rc.linkup: Gateway, NONE AVAILABLE
Nov 20 20:51:58 pfSense php-fpm[12259]: /rc.linkup: Hotplug event detected for LAN(lan) dynamic IP address (4: 192.168.1.1, 6: track6)
Nov 20 20:51:58 pfSense php-fpm[12259]: /rc.linkup: DEVD Ethernet attached event for lan
Nov 20 20:51:58 pfSense php-fpm[12259]: /rc.linkup: HOTPLUG: Configuring interface lan
Nov 20 20:51:58 pfSense php-fpm[12259]: /rc.linkup: Gateway, NONE AVAILABLE
Nov 20 20:51:58 pfSense php-fpm[12259]: /rc.linkup: Gateway, NONE AVAILABLE
Nov 20 20:51:58 pfSense php-fpm[42325]: /rc.linkup: Hotplug event detected for LAN(lan) dynamic IP address (4: 192.168.1.1, 6: track6)
Nov 20 20:51:58 pfSense php-fpm[42325]: /rc.linkup: DEVD Ethernet attached event for lan
Nov 20 20:51:58 pfSense php-fpm[42325]: /rc.linkup: HOTPLUG: Configuring interface lan
Nov 20 20:51:58 pfSense php-fpm[42325]: /rc.linkup: Gateway, NONE AVAILABLEBut eventually it works.
-
The dongle is this:
"ugen0.4: <ASIX Elec. Corp. AX88179> at usbus0"
-
Hmm, USB NICs are generally badly regarded in FreeBSD/pfSense. Those ASIC based NICs are usually the best you can hope for but if you can use anything other than USB you should do that.
-
Same for me - Intel NUC with USB NIC for WAN. I have to stay on 2.7.0, 2.7.1 or 2 doesnt work. NGINX issue.
Is there posibility to use different drivers, that were in 2.7.0 together with 2.7.2 version?
-
You might be able to use a driver for the specific hardware rather than the cdce driver. It's possible some specific driver gained support for that hardware in 2.7.1/2.7.2 and that's what changed.
