After installing 24.7 and restoring my config backup everything seemed to be OK. But after update from 24.7 to 24.7.1 my dashboard is now empty and options "Restore default layout" and "Add Widget" do nothing, i.e. after clicking on "Restore default layout" nothing happens and after clicking on "Add Widget" pull-down menu which should contain list of widgets is not opening and contains only "Nothing selected" line. I rebooted box after update to 24.7.1.
Edit: yes, I cleared cache/cookies in browser and tried different "fresh" browser.
Upgrade one instance of 24.1.10 to 24.7.1 from GUI, all went well, confirmed kernel (uname -a) and base system updated well and health check shows no problems.
However, the Lobby is completely empty, no reaction if I reset to default and no widgets to select from "Add" drop-down.
Little lost here. Tried 3 different clients with palemoon browser. Only success in Firefox...
Quote from: chemlud on August 15, 2024, 05:58:42 PM
Little lost here. Tried 3 different clients with palemoon browser. Only success in Firefox...
Probably helps to use a browser someone else is actually using. Downloaded the latest version from their website, after installing on W11 it only produces a nifty crash on launch. Good luck.
No windows here ;-)
Ok, the 32bit version actually "works". That is, it runs. Now, I can see a heap of javascript errors in the F12 console and that's it.
"Error resolving module specifier: widget-base-table"
Failed initializing Widgets Error: No widgets loaded
Stack trace:
_initializeWidgets@https://gw.example.com/ui/js/opnsense_widget_manager.js?v=caa0760339baa1dd:153:19
initialize@https://gw.example.com/ui/js/opnsense_widget_manager.js?v=caa0760339baa1dd:110:18
Afraid you are on your own attempting to fix this.
I guess palemoon times are over for opnsense. have to move to FF, the browser that smells a little like an old used-car salesman. However, the others smell purely rotten :-D
What about a Chromium based browser without Google's surveillance - like e.g. Brave?
Had a look
https://brave.com/linux/#release-channel-installation
What I really like(d) about palemoon: No installation, no repo needed, simply run from directory after download/unpack. Do update from time to time from running browser.
I have just talked to the Palemoon core dev (yeah I know them, quite random that Palemoon pops up here) and the browser does not support this feature:
<script type="importmap">
It was added by the OPNsense in this commit:
https://github.com/opnsense/core/commit/c73f63c3fa7271f28192d66f8a6f1280e0ca0c2c
This makes the Dashboard totally incompatible with Palemoon in 24.7.1.
They lack funds to implement this feature since it is very complex and tricky. They need more monetary support. They have added an issue to their core repo. I'll link it here soon.
Please support this browser if you use and like it, there are not many alternatives out there anymore.
https://repo.palemoon.org/MoonchildProductions/UXP/issues/2556
Hi and thanks Frankfurt! ;-)
What are we talking about? 50, 500 or 5000 bucks? ;-)
In the last months the logs for some opnsense didn't load in palemoon, too. But worked well in FF.
I dont know the money amount but they said it would take around 40-80 hours to implement.
The import maps are a google sponsored spec for chrome to give them a competetive advantage over other browser engines. They do these things whenever they can to hurt Mozilla based browsers.
If you disagree with this import map implementation in OPNsense you can also open an issue on the opnsense github and link this thread.
Don't disagree, not an expert at all and your analysis sounds plausible to a non-expert. ;-)
I mean like, if you would like to signal that you have an issue, open it on github.
Maybe this change can be reverted for better browser compatability.
But without somebody raising the issue who uses alternative browsers, its harder to justify the need for it. So please raise your hand.
Hi, tickets are not my world, how about you raising the issue and link it with this thread? :-)
Have no paypal (and don't trust it), so have to find adifferent way to support palemoon project...
https://github.com/opnsense/core/issues/7777
Quote from: Monviech on August 15, 2024, 08:19:55 PM
I mean like, if you would like to signal that you have an issue, open it on github.
Maybe this change can be reverted for better browser compatability.
But without somebody raising the issue who uses alternative browsers, its harder to justify the need for it. So please raise your hand.
I am using only non-Microsoft and non-Chrome browsers. Same in company I work for (decided by IT higher-ups for security reasons).
OPNSense devs should not experiment with fancy gadgets which are aimed to be a weapons in war of Google with its competitors. And right now I can't even see the vital stats and states of OPNSense.
Well then explain your usecase in the ticket I have raised. Its up for discussion.
Quote from: Monviech on August 15, 2024, 07:23:16 PM
I have just talked to the Palemoon core dev (yeah I know them, quite random that Palemoon pops up here) and the browser does not support this feature:
<script type="importmap">
It was added by the OPNsense in this commit:
https://github.com/opnsense/core/commit/c73f63c3fa7271f28192d66f8a6f1280e0ca0c2c
This makes the Dashboard totally incompatible with Palemoon in 24.7.1.
They lack funds to implement this feature since it is very complex and tricky. They need more monetary support. They have added an issue to their core repo. I'll link it here soon.
Please support this browser if you use and like it, there are not many alternatives out there anymore.
https://repo.palemoon.org/MoonchildProductions/UXP/issues/2556
Quote from: Monviech on August 15, 2024, 08:19:55 PM
I mean like, if you would like to signal that you have an issue, open it on github.
Maybe this change can be reverted for better browser compatability.
But without somebody raising the issue who uses alternative browsers, its harder to justify the need for it. So please raise your hand.
Quote from: chemlud on August 15, 2024, 08:25:39 PM
Hi, tickets are not my world, how about you raising the issue and link it with this thread? :-)
Have no paypal (and don't trust it), so have to find adifferent way to support palemoon project...
Quote from: Monviech on August 15, 2024, 09:45:22 PM
Well then explain your usecase in the ticket I have raised. Its up for discussion.
Wow. I'm not affected but thanks for doing this Moviech. You've gone well out of your way to help.
I imagine many would have understood if you had insisted on the issue/ticket being opened by the user in github.
Discussion was ended with "won't fix". That's why I don't waste my time with "tickets" and alike.
My time is little...
Quote from: chemlud on August 16, 2024, 09:29:57 AM
My time is little...
Well I'd say the same is valid for OPNsense developers. These browsers have virtually non-measurable user base, (literally) a couple of developers and contributors. Keeping up with the web standards development is apparently not a realistic goal for such projects.
Dunno, maybe the Palemoon & co. guys should rebase their forks (of other forks) once again - since otherwise it's just reinventing the wheel and a lost cause... But this seems to be sort of religious topic everytime it comes up - not just here, see this reddit thread (https://www.reddit.com/r/browsers/comments/12g5ssz/does_the_development_of_the_goanna_browser_engine/), e.g. ;D :o
Quote from: rackenthogg on August 15, 2024, 09:32:19 PM
I am using only non-Microsoft and non-Chrome browsers. Same in company I work for (decided by IT higher-ups for security reasons).
That does not rule out Safari and Firefox so you still have two options supporting current standards.
It wasn't ended with "won't fix" as far as I can see. (my emphasis). It seems more like "put something there official" so we have the official item for discussion amongst devs.
Quote from: Monviech on August 15, 2024, 08:19:55 PM
I mean like, if you would like to signal that you have an issue, open it on github.
Maybe this change can be reverted for better browser compatability.
But without somebody raising the issue who uses alternative browsers, its harder to justify the need for it. So please raise your hand.
Quote from: chemlud on August 16, 2024, 09:29:57 AM
Discussion was ended with "won't fix". That's why I don't waste my time with "tickets" and alike.
My time is little...
You see, this is where I find it strange. Opening a ticket in github takes a few minutes. That is the system used by the project. Strange for me is the view that tickets are a waste of time. I guess you've never had to deal with support services that require a ticket. Not optional, one must be raised, regardless if they have forum or not. Forums are for most companies not a support system, and if you were to comply with best practice -for example- ITIL, there must be a system of record with "requests", "incidents", "changes", and the rest. But if you haven't and all places you require your issue to have attention by someone in the organisation accept a forum post, fair enough.
Not picking on anyone, just honestly I find it hard to understand we're using a product, some of us for free. Then we have a very niche problem, we report/query it in the forum and when asked to spend a few minutes to log it in github, we say we have no time to waste with doing that.
So the new staffer goes and does it himself after hearing "Hi, tickets are not my world, how about you raising the issue and link it with this thread? :-)" . That is just taking whatever it is to a whole new level.
Moving on now, I sound too preachy now.
I'll just leave this here. https://github.com/opnsense/core/issues/7777#issuecomment-2293192128
Ok here we have it. Nobody bothered to report back on this. It really can't be that important.
Cheers,
Franco
tbh, I simply don't use the Dashboard anymore. Have an empty landing page for GUI and that's about it. Most info can be retrieved from some other place, rest is gone with the wind.
No offence intended.
I'll ship this when someone who asked for it tries it. Not before.
Cheers,
Franco
Did some testing. As for results, see the linked Github issue. I won't spend any more time on this. Who wants this working needs to produce some effort of their own to help with this.
Dashboard is extremely important to me. How to test it? My current OPNSense build is the buggy one (OPNSense 24.7.2 "Kernel panic") reinstalled on UFS filesystem. How to install test build to check the dashboard? Is it in development repo?
Quote from: franco on August 26, 2024, 09:05:48 AM
Ok here we have it. Nobody bothered to report back on this. It really can't be that important.
Cheers,
Franco
Quote from: rackenthogg on August 26, 2024, 01:13:31 PM
Dashboard is extremely important to me. How to test it?
https://github.com/opnsense/core/issues/7777
No test build, no development repo, simple patch.
Quote from: doktornotor on August 26, 2024, 01:19:18 PM
Quote from: rackenthogg on August 26, 2024, 01:13:31 PM
Dashboard is extremely important to me. How to test it?
https://github.com/opnsense/core/issues/7777
No test build, no development repo, simple patch.
My eyes are full of tears of joy. Widgets works on older Firefox, Palemoon and Basilisk. They are also editable: I can add widgets.
Yeah they display and you can add/remove. Resize / drag doesn't work for me. Have fun.
Quote from: rackenthogg on August 26, 2024, 01:52:15 PM
My eyes are full of tears of joy. Widgets works on older Firefox, Palemoon and Basilisk. They are also editable: I can add widgets.
Let's ship it in 24.7.3 then.
Thanks,
Franco
What would be the latest patch to test? Maybe can test tonight...
https://github.com/opnsense/core/issues/7777#issuecomment-2309669493
Ok, did
"opnsense-patch e2bd3c3"
and tried with FF 129.2 and Palemoon 33.2.1 (both Linux).
Can add Widgets to Dasboard (both browsers), but can't move/resize them in Palemoon (but FF).
So fixed, somehow (not). :-)
Quote from: chemlud on August 26, 2024, 05:55:20 PM
Can add Widgets to Dasboard (both browsers), but can't move/resize them in Palemoon (but FF).
Yes, matches my observations then. Should be followed up on Github.
btw: in Palemoon the logs for Unbound or ISCDHCPv4 won't load (for months at least), as described above...
Yeah, apparently that browser is missing many more bits beyond importmap.
I think that "there is nothing at all" to "there is something" a quite positive improvement.
If there are other browser specific issues, they should be raised at the repos of their maintainers.
Indeed. Or perhaps with Palemoon devs. Things working on old ESR FF versions broken there, really?
Well, let's ship and see. There's no point in speculating over what's wrong at the moment as the exact change is coming now as requested and nothing else will be done to avoid further problems. From Safari, Firefox and Chrome it looks good either way.
Cheers,
Franco