Configure WAN interface produces Uncaught TypeError

When I logged into the Cockpit interface to Nethserver, there was a warning that one of the DNS servers was not responding, so I looked at the Network config. I don’t think the DNS not responding is related to the following bug, but it was the reason why I looked at the WAN config, and the warning disappeared after the various operations I did described herein.

From the Network panel in Cockpit, I selected the Configure button on the WAN interface, clicked the Next button, then Configure on the next pane.

I made no changes, but selected Nest and Configure.

When it applied, Cockpit popped up an error with a prompt to refresh the browser, or use CTRL-SHIFT-J to open the Javascript console, and displays a red “Ooops!” in the upper right next to the admin userid icon and username.

The Javascript console showed one error at the bottom:

Uncaught TypeError: Cannot read property ‘length’ of app.016b4eb3.js:1
undefined
at app.016b4eb3.js:1
at Function. (nethserver.js:108)
at s (cockpit.min.js:963)
at cockpit.min.js:975
at n (cockpit.min.js:881)

Repeating the process produced the same error.

1 Like

I confirm the issue. Same Ooops here.

Thank you for reporting, we will look into it.

Just a question: is the oops just cosmetic or the page doesn’t work correctly?

I’d say cosmetic.

1 Like

Hi, thank you for reporting.
This commit should fix the problem.
Can you try again with nethserver-cockpit installed from testing repo.

fix verified.

1 Like

Fails for me with the version in testing repo.with Javascript console message, and red Ooops!

I did:
yum --enablerepo=nethserver-testing install nethserver-cockpit

Note however, I did not try this until today, after I ran the large regular update and then rebooted.

Diagnostic in Javascript console:
Uncaught TypeError: Cannot read property ‘length’ of undefined
at app.016b4eb3.js:1
at Function. (nethserver.js:108)
at s (cockpit.min.js:963)
at cockpit.min.js:975
at n (cockpit.min.js:881)

With the latest updates (today 6Feb2020) it works correctly, no Ooops! message. Thank you for fixing.