Log Browser
-
In pfBlockerNG menu->log there is a log browser. I get nothing when I make a selection for any of the choices.
File Type: Log Files
File Selection: pfblockerng.log
The file /var/log/pfblockerng/pfblockerng.log clearly exists, as do the other possible file selections that also do not display.Using SG-2440 appliance and v2.4.4
I had this problem with v2.4.3 but some of the other file selections would display. Now nothing displays.
Just looking for some ideas on how to fix this at my end. -
What browser? Can you try in another browser? Any Browser extension that might be blocking it?
-
I'm logged into the pfSense GUI from an iMac client, using Safari as a browser. I am running only one extension in Safari, trafficlight by BitDefender which lists web trackers. It marks the pfSense as 'Safe Page'. I also whitelisted pfSense in the extension but that should not be necessary.
I also tried w/ all extensions disabled. No luck there either.
I just fired up a linux computer w/ FireFox - it works as expected, good call on changing browser, but this is also changing computers.
So I wonder what it is about the iMac that is blocking the viewer from working. Everything else in the GUI seems to work fine. -
@jonh What about Firefox or Chrome for MAC ?
-
That is what I'd consider as a last ditch option. I'd rather keep my system with a single browser. I hope to discover why it does not display rather than add a different browser. It would be useful to know if there are other users of pfSense w/ pfblockerng that use a Safari browser and if they also have problems. Perhaps I have pfSense mis-configured. I don't want to jump before I've walked.
-
Doing a test with another browser will help you find out if it is Safari or the MAC that is causing the problem.
-
@bbcan177
I booted osX to 'Safe Boot' and have the same issue.I'm not a coder but looked at your PHP and note Ajax handles the Post request. On the web there are a lot of older comments about Safari not working well with Ajax, in some cases work arounds are posted but I don't know if they are applicable to this problem.
I also checked with a Mac laptop and it has the same issue.
I don't have a problem with the System logs, only the pfBlockerNG logs.
@RonpfS
I really want to avoid installing FF. I agree it is a good diagnostic but if I can work around it by using a different computer for the occasional of that page. Or I can simply download the applicable log file and read it as text. Web searches about Ajax & Safari pretty much convinces me that Safari is the likely issue. -
@bbcan177
FWIW, I installed a linux distro in a VM running on my iMac. Firefox works correctly with the log browser.
I assume that as I posted earlier, this problem has to do with Safari and possibly Ajax.Is there any hope of a solution?
-
Can't help you with "osX on MAC" but I have a iPhone and thus Safari.
Can consult the pfSense GUI just fine with my iPhone.Now I think out load : if Safari on an iPhone works, then it should also work on a "real" Mac. Right ?
-
Using chrome on mac here. Select a log file to view, and then select the same one again, and the file will load. It seems like a minor bug.
-
@gertjan said in Log Browser:
if Safari on an iPhone works, then it should also work on a "real" Mac.
Thank you for this observation. I don't think I have ever attempted to open pfSense with my iOS devices.
Yes, iPhone & iPad both work. The iPhone is much faster for some reason. They are both updated to latest iOS and on same wifi network.That said, still no luck with Mac on Safari. None of the possible files open in the log browser. However, the MacOS is not the same as iOS. Maybe the OS of these devices is different enough that allows iOS to work but not MacOS?
I don't look at the log browser often. But in the past it has worked. That was when the MacOS was High Sierra, now I am running Mojave.
-
@bfeitell said in Log Browser:
Using chrome on mac here. Select a log file to view, and then select the same one again, and the file will load. It seems like a minor bug.
The above sequence of double selection is how it works for me in iOS. It doesn't work for the MacOS.
When I was running the prior version, High Sierra, it required this double selection. However, once it showed the contents of the selected file, As long as I didn't change the first parameter, 'file type', I could then change the file selection and choose the 'reload' icon that appeared next to the log contents and the next selection would load immediately, without a double selection.Since you have a Mac, can you check Safari to see if it fails on your Mac?
-
Double selection works in Safari for me, but I am stuck on an older version of MacOS.
Safari Version 11.1.2 (11605.3.8.1) -
@bfeitell said in Log Browser:
but I am stuck on an older version of MacOS.
Good reason not to update at this time.
-
Topic seems to be 2 months old, but I'm new and also trying to resolve this problem.
Running safari 12.x on Mac 10.14.x (mojave). Cannot get any logs to appear, even when doing the "select again" trick.
Seems to work on Chrome though but requiring still requiring twice selecting the log file.
I can live with that. Not really looking for a fix or answer, but saying if you're on a Mac and the log browser doesn't work for you in Safari, try another browser along with selecting the log file from the drop down list an extra time or two.
-
@yyz said in Log Browser:
Running safari 12.x on Mac 10.14.x (mojave). Cannot get any logs to appear, even when doing the "select again" trick.
FWIW, latest OSX update did not fix it. And latest iOS update still allows multiple selection to work. But then you have a logfile that is frustratingly long to browse through on a little screen. I find it easier to load a VM and use either Windows or Linux to view these logs. Or to used Diagnostics menu->command prompt or Edit to browse the log.
I've read comments at various sites that this Safari issue may be related to Ajax. I don't know if that is applicable to pfBlockerNG or not.
-
Just saw this thread. FYI, it looks like we have the same problem on macOS 11.6 with Safari 15.0 running on an MBA M1. It works fine with Chrome on the same machine.
-
@sozler
Wow! My post was 3 years ago!
I’ve stopped using pfsense and therefore pfblockerNG quite some time ago.
I’m using https://nextdns.io now. It’s pretty good and much easier to use and configure. (It’s far from perfect, but it’s way simpler)
