Webtop 5: HTTP Status 404 - Not Found

[Shadowfire (Jeff Davis)]

NethServer Version: 8
Module: webtop

After updating my NethServer 8. The core seems to have upgraded fine.

I did a reboot of NethServer 8. After that I did an update on all the things I am running on NethServer 8.

I thought everything went through with everything for all the apps updates.

But later on I went back to look at my email from Webtop and that is when I found the following.

I was thinking I might need to check the status of the Webtop webserver first and see if it is running. But I am unsure what command that is. Also I figured I probably need to restart the webserver for Webtop. I am unsure what that command is either.

I went to -

WebTop groupware — NS8 documentation

To see if it has commands related to what I should do next, but I don’t see ones that would help.

Any thoughts as to why this is happening?

[mrmarkuz (Markus Neuberger)]

Is there something in the logs?

With the newest core it’s possible to restart app instances from Software Center.

On CLI you could try to restart the webtop-apache container:

runagent -m webtop1 systemctl --user restart apache

[Shadowfire (Jeff Davis)]

I tried to restart the Webtop from WUI and from CLI. It did not make a difference. Externally I am getting the same message.

I notice externally that the address is saying -

https://webtop.mycomputervisions.com/webtop/

instead of

https://webtop.mycomputervisions.com

internally I see the following now…

404 page not found

Before I did the updates everything was working ok externally and internally. Is it possible that there may be a problem with Traefik settings now?

Can I go into the Webtop settings and save them again? Would that cause a problem or make a difference?

If I re-save the settings in Webtop settings will it rebuild the Traefik route and clear up issue or not really?

[mrmarkuz (Markus Neuberger)]

@Shadowfire

Can I go into the Webtop settings and save them again? Would that cause a problem or make a difference?

If I re-save the settings in Webtop settings will it rebuild the Traefik and clear up issue or no?

It’s worth a try. Reconfigure the app shouldn’t cause issues.

The traefik route should be fixed by saving the settings.

Please check and share the Webtop traefik route:

EDIT:

Please also check running containers:

runagent -m webtop1 podman ps

…and images:

runagent -m webtop1 podman images

[Shadowfire (Jeff Davis)]

Okay. I re-saved settings.

Looks like the port is different, but that is the only thing I a can see that is different.

But that would be it. Is that an issue?

[mrmarkuz (Markus Neuberger)]

No, it looks ok.

Did you maybe customize Webtop as explained here?

@mrmarkuz

Please also check running containers:

runagent -m webtop1 podman ps

…and images:

runagent -m webtop1 podman images

[Shadowfire (Jeff Davis)]

So my Webtop is Webtop5

This is what I see …

[mrmarkuz (Markus Neuberger)]

@Shadowfire

So my Webtop is Webtop5

Are there more Webtop instances running?

Do you use Rocky or Debian?

There are more ports listed on my side:

[root@node ~]# runagent -m webtop1 podman ps
CONTAINER ID  IMAGE                                     COMMAND           CREATED            STATUS            PORTS                              NAMES
febe97a266b5  localhost/podman-pause:5.2.2-1746548935                     About an hour ago  Up About an hour  0.0.0.0:20022->8081/tcp            8a7cc3b82f86-infra
72eaf1dd6014  ghcr.io/nethserver/webtop-postgres:1.5.0  postgres          About an hour ago  Up About an hour  0.0.0.0:20022->8081/tcp, 5432/tcp  postgres
0fbb59d72132  ghcr.io/nethserver/webtop-apache:1.5.0    httpd-foreground  About an hour ago  Up About an hour  0.0.0.0:20022->8081/tcp, 80/tcp    apache
3836e5451632  ghcr.io/nethserver/webtop-webapp:1.5.0    catalina.sh run   About an hour ago  Up About an hour  0.0.0.0:20022->8081/tcp, 8080/tcp  webapp
d1ca93ec6e05  ghcr.io/nethserver/webtop-webapp:1.5.0                      About an hour ago  Up About an hour  0.0.0.0:20022->8081/tcp, 8080/tcp  pecbridge
501a9f9ad790  ghcr.io/nethserver/webtop-webdav:1.5.0    php-fpm           About an hour ago  Up About an hour  0.0.0.0:20022->8081/tcp, 9000/tcp  webdav
3e5ed41bc8fa  ghcr.io/nethserver/webtop-z-push:1.5.0    php-fpm           About an hour ago  Up About an hour  0.0.0.0:20022->8081/tcp, 9000/tcp  z-push

[root@node ~]# runagent -m webtop1 podman images
REPOSITORY                           TAG               IMAGE ID      CREATED      SIZE
ghcr.io/nethserver/webtop            1.5.0             5448b287a34a  13 days ago  8.91 MB
ghcr.io/nethserver/webtop-phonebook  1.5.0             b64c604a0de2  13 days ago  123 MB
ghcr.io/nethserver/webtop-z-push     1.5.0             e18bc9e8b358  13 days ago  81.5 MB
ghcr.io/nethserver/webtop-webdav     1.5.0             72284a6a52c9  13 days ago  71.5 MB
ghcr.io/nethserver/webtop-apache     1.5.0             0240ab11b83a  13 days ago  138 MB
ghcr.io/nethserver/webtop-postgres   1.5.0             944819883c5a  13 days ago  462 MB
ghcr.io/nethserver/webtop-webapp     1.5.0             8362aa57531c  13 days ago  467 MB
localhost/podman-pause               5.2.2-1746548935  e3ec47902085  3 weeks ago  813 kB

[Shadowfire (Jeff Davis)]

I only have one node running. It should only be one instance of Webtop5 running on this node.

It is running on Debian.

Can you clarify more ports listed on your side? I am not sure I follow you.

[mrmarkuz (Markus Neuberger)]

For example the postgres container has ports 0.0.0.0:20022->8081/tcp, 5432/tcp on my side.
In your screenshot the 5432/tcp is missing.

72eaf1dd6014  ghcr.io/nethserver/webtop-postgres:1.5.0  postgres          About an hour ago  Up About an hour  0.0.0.0:20022->8081/tcp, 5432/tcp  postgres

Are there maybe old HTTP routes from the older Webtop instances in the HTTP routes or do you use the Webtop FQDN more times in the HTTP routes?

[Shadowfire (Jeff Davis)]

It doesn’t look like it… I tried to pull up the following.

So I am thinking I don’t have Webtop1 instances. I also checked for Webtop2, Webtop3. Webtop4 as well and got the same error message as above.

Hmmm so I went under logs and found the following -

Fun…. Thoughts…

[mrmarkuz (Markus Neuberger)]

Did you select the right mail server instance in the Webtop settings?

Is the mail server running?

runagent -m mail1 podman ps

[Shadowfire (Jeff Davis)]

I believe it is the correct mail server - (The only selection)

This is what it shows running -

So I can still get email from my phone via email app (not web). But I am unable to get on Webtop from logon from pc browser. It still errors out and will not go to Logon page.

[mrmarkuz (Markus Neuberger)]

I tested Webtop 1.5.0 on Debian now and couldn’t reproduce the issue.

Maybe it helps to restart the pecbridge?

runagent -m webtop5 systemctl --user restart pecbridge

[Shadowfire (Jeff Davis)]

@mrmarkuz

runagent -m webtop5 systemctl --user restart pecbridge

well, it didn’t get the WUI up and running, but I went back in to logs and found the following.

says -

 SLF4J: The requested version 1.7.16 by your slf4j binding is not compatible with [1.6]
2025-09-15T05:16:08-04:00 [1:webtop5:pecbridge] SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.

and

 ERROR com.sonicle.pecbridge.Configuration - Webtop Api Error
2025-09-15T05:16:09-04:00 [1:webtop5:pecbridge] com.sonicle.webtop.core.cli.ApiException: error

@webtop_team

Said to check this out -

SLF4J Error Codes

Not sure if this is really why I am having my issue, but thought I would at least put up here.

[mrmarkuz (Markus Neuberger)]

Could you please share the webtop log after reconfiguring (save app settings) the instance?

EDIT:

Please share it as text, not as screenshot.

EDIT2:

@Shadowfire please also check/share the webtop.properties file:

runagent -m webtop5 cat webtop.properties

EDIT3:

@Shadowfire I found it in the logs that you sent me and I could reproduce.

Sep 15 05:54:07 cvserver1 postgres[27950]: 2025-09-15 09:54:07.170 UTC [34] FATAL: invalid value for parameter "TimeZone": "US/Eastern"

The timezone “US/Eastern” doesn’t work, you could use “America/New_York” instead which works here…

EDIT4:

Bug issue opened.

Webtop doesn't start when "US/*" timezones are set

[Shadowfire (Jeff Davis)]

I did change the timezone to America/New_York. I then looked at the logs. It looks like all the errors are gone now that I can tell.

I am testing externally and it looks like it is working externally now. WOOHOO! That was it. wow!

2025-09-15_09-591607×930 148 KB

That gets external working properly. Major win!

[Shadowfire (Jeff Davis)]

Interestingly the internal is still not working.

I don’t think it is OPNSense. I don’t think I made any changes that would affect that side. I am going to recreate the local Traefik route.

Just curious… I know under Node 1 firewall and Public zone services - I see zone services for dhcpv6-client / ejabberd1 / http / https / mail1 / nethvoice-proxy3 / nethvoice5 / ns-wireguard / samaba2 / ssh

Should I see one for webtop5?

[mrmarkuz (Markus Neuberger)]

No, Webtop doesn’t need a firewall setting as it just uses HTTP/HTTPS.

Did you set an internal DNS record for Webtop? If not you may need to enable Hairpin NAT/NAT reflection on the opnsense to follow the port forward from inside LAN.

[Shadowfire (Jeff Davis)]

I originally made a Traefic local route, by /webtop. I removed that and I setup a OPNSense NAT rules manually with Method 1 prevents unwanted traffic and makes auditing easy.

I can now access Webtop local as well now.

This has me up and running now. Thank you my friend. You are an amazing addition to NethCommunity!