Log Browser always empty
-
@jonh said in Log Browser always empty:
Through various versions of Mac OS and Safari updates
As I have an iPhone, thus iOS (latest) and Safari, I accessed pfSense.
All the log pages showed up just fine.
I know this doesn't mean anything, but I really believe that as my 'mini'" Safari works, why shouldn't the desktop version work ?As soon as you receive someone at your place using an iPad or better : iMac, ask him to test.
And say to yourself : the only difference is : our local browser settings ^^ -
@jonh
It works fine in safari on my iPad running latest version of iOS. Does not work on safari on my MacBook running Big Sur. I don’t have any addons installed on safari on my MacBook. -
@gertjan said in Log Browser always empty:
As soon as you receive someone at your place using an iPad or better : iMac, ask him to test.
And say to yourself : the only difference is : our local browser settings ^^I agree with your comment if the 'mini' works why doesn't the desktop.
I never have bothered to use my mobile devices to access pfSense. My ancient eyeballs have enough issues with basic mobile device usage. That said, my iPhone and my iPad Pro both access the said log files (thanks for the suggestion). I borrowed a new macbook and it does not access the log files. iOS does not specify iOS build version of Safari other than it is the same base version of the underlying iOS (v14 in my case, more specifically, v14.4.2)
The borrowed MacBook, runs macOS, same as my iMac. Same version (11.2.3) also. And Safari versions are identical, (14.9.3 (16610.4.3.1.7)).
So, pfBlocker logs render just fine in iOS but not macOS. I doubt my local browser settings are an issue, no added extensions. The borrowed macBook also has no extensions. I will review my macOS Safari settings but as vjizzle noted recently, he observes the same issues as myself.
I will note that in recent years gone by there have been some functional differences w/ Safari between iOS apps and macOS apps, I don't recall at this moment what they were.
Anyway, thanks so much for the well deserved kick in the pants (ie: I should have thought of this myself), at least I can now use my iPad to check these log files rather than access them via the pfSense Diagnostics menu or firing up my linux machine.
-
Hi folks,
So the problem still exists obviously, and I went ahead and did a test across platforms to confirm:
macOS Big Sur 11.2.3 w/ Safari 14.0.3 = NOTHING DISPLAYED
iPhone iOS 14.4.2 = ALWAYS WORKS
iPadOS 14.4.2 = ALWAYS WORKS- The moment you select a log file on mobile devices, it displays it.
- It never works on desktop Safari (no extensions); I gave up and use Firefox for that purpose.
-
@jonh said in Log Browser always empty:
@gertjan said in Log Browser always empty:
As soon as you receive someone at your place using an iPad or better : iMac, ask him to test.
And say to yourself : the only difference is : our local browser settings ^^I agree with your comment if the 'mini' works why doesn't the desktop.
I never have bothered to use my mobile devices to access pfSense. My ancient eyeballs have enough issues with basic mobile device usage. That said, my iPhone and my iPad Pro both access the said log files (thanks for the suggestion). I borrowed a new macbook and it does not access the log files. iOS does not specify iOS build version of Safari other than it is the same base version of the underlying iOS (v14 in my case, more specifically, v14.4.2)
The borrowed MacBook, runs macOS, same as my iMac. Same version (11.2.3) also. And Safari versions are identical, (14.9.3 (16610.4.3.1.7)).
So, pfBlocker logs render just fine in iOS but not macOS. I doubt my local browser settings are an issue, no added extensions. The borrowed macBook also has no extensions. I will review my macOS Safari settings but as vjizzle noted recently, he observes the same issues as myself.
I will note that in recent years gone by there have been some functional differences w/ Safari between iOS apps and macOS apps, I don't recall at this moment what they were.
Anyway, thanks so much for the well deserved kick in the pants (ie: I should have thought of this myself), at least I can now use my iPad to check these log files rather than access them via the pfSense Diagnostics menu or firing up my linux machine.
Ah, you beat me to it by a second!
-
Hello,
Thank you for this thread. I have the same issue since some months. So I just downloaded chromium and tried: Boum ! It works, it displays the logs.
I know this thread is quite old, that's why I was wondering if there is any solution yet from negate team ?
We must be a lot of people using a Mac and pfsense.Kind regards.
-
@p_bear
OP here. It does work on other browsers, I tried a couple on different OS's. But I use Safari on my main desktop and I'm not interested in installing a different browser on my Mac. I can boot a linux box and use FF or I can ssh into pfSense and drill down to the log location. Or, as Gertjan so kindly pointed out, it works fine in iOS. I find using iOS for this purpose clumsy, mainly due to my motorskills have deteriorated with my age. I have just accepted it as something that is not going to get fixed, be it Apple's issue or Netgate's issue. For me, I simply no longer check the log unless I observe an issue. -
@jonh
Same here, I don't want to keep and launch an alternative browser, just to be able to display a part of the interface of Pfsense.Apple's issue or Netgate's issue .. well I don't believe Apple will adapt something anytime soon in Safari to make it functional with Pfsense.
So the ball is in the court of Netgate to adapt their interface and make it work correctly with Safari. -
Same here.
iOS 15.1.1 > Safari 15.1 = logs are displayed.
macOS 12.0.1 > Safari 15.1 (no extensions installed) = logs are not displayed. -
@emikaadeo
Well, I'm under 2.6dev version and it still has this bug. It looks like netgate cannot care less. It's probably more easy for them to blame Apple. -
@p_bear I don’t know who to blame but if a 3rd party browser works but Safari does not it seems that Netgate is not to blame. It would be nice to know why it does not work so we have something useful to complain to Apple about.
It used to work, I forget if it first broke when Yosemite was released?
