<![CDATA[WebUI 4.2: HTTP ERROR 404. Problem accessing /.]]>Just upgraded NetXMS from 4.1 to 4.2. We also upgraded WebUI by replace the war files with:
netxms-websvc-4.2.395.war
nxmc-legacy-4.2.395.war

When restarting the Windows service nxWebUI it takes at least a few minutes until it starts responding on port 80. nxwebui.log doesn't show any obvious errors:

2022-10-24 16:45:31.934:INFO:oejs.ServerConnector:ShutdownMonitor: Stopped ServerConnector@57aa341b{HTTP/1.1}{0.0.0.0:80}
2022-10-24 16:45:31.943:INFO:oejsh.ContextHandler:ShutdownMonitor: Stopped o.e.j.w.WebAppContext@1725dc0f{/api,file:/C:/NetXMS-WebUI/base/api/webapp/,UNAVAILABLE}{C:\NetXMS-WebUI\webapps\api.war}
2022-10-24 16:45:32.070:INFO:oejsh.ContextHandler:ShutdownMonitor: Stopped o.e.j.w.WebAppContext@31368b99{/,file:/C:/NetXMS-WebUI/base/nxmc/webapp/,UNAVAILABLE}{C:\NetXMS-WebUI\webapps\nxmc.war}

2022-10-24 16:45:33 Apache Commons Daemon procrun stderr initialized.
2022-10-24 16:45:34.215:INFO::main: Logging initialized @219ms
2022-10-24 16:45:34.282:INFO:oejr.Runner:main: Runner
2022-10-24 16:45:34.469:INFO:oejs.Server:main: jetty-9.2.19.v20160908
org.w3c.css.sac.CSSException: Failed to read property cursor: Invalid value for cursor: hand
org.w3c.css.sac.CSSException: Failed to read property cursor: Invalid value for cursor: hand
2022-10-24 16:45:41.005:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@31368b99{/,file:/C:/NetXMS-WebUI/base/nxmc/webapp/,AVAILABLE}{C:\NetXMS-WebUI\webapps\nxmc.war}
2022-10-24 16:45:41.513:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@1725dc0f{/api,file:/C:/NetXMS-WebUI/base/api/webapp/,AVAILABLE}{C:\NetXMS-WebUI\webapps\api.war}
2022-10-24 16:45:41.514:WARN:oejsh.RequestLogHandler:main: !RequestLog
2022-10-24 16:45:41.534:INFO:oejs.ServerConnector:main: Started ServerConnector@2d08304a{HTTP/1.1}{0.0.0.0:80}
2022-10-24 16:45:41.535:INFO:oejs.Server:main: Started @7546ms
2022-10-24 16:46:05.520:INFO:oejs.ServerConnector:ShutdownMonitor: Stopped ServerConnector@2d08304a{HTTP/1.1}{0.0.0.0:80}
2022-10-24 16:46:05.531:INFO:oejsh.ContextHandler:ShutdownMonitor: Stopped o.e.j.w.WebAppContext@1725dc0f{/api,file:/C:/NetXMS-WebUI/base/api/webapp/,UNAVAILABLE}{C:\NetXMS-WebUI\webapps\api.war}
2022-10-24 16:46:05.891:INFO:oejsh.ContextHandler:ShutdownMonitor: Stopped o.e.j.w.WebAppContext@31368b99{/,file:/C:/NetXMS-WebUI/base/nxmc/webapp/,UNAVAILABLE}{C:\NetXMS-WebUI\webapps\nxmc.war}

2022-10-24 16:46:07 Apache Commons Daemon procrun stderr initialized.
2022-10-24 16:46:07.771:INFO::main: Logging initialized @218ms
2022-10-24 16:46:07.830:INFO:oejr.Runner:main: Runner
2022-10-24 16:46:08.006:INFO:oejs.Server:main: jetty-9.2.19.v20160908
2022-10-24 16:48:14.726:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@31368b99{/,file:/C:/NetXMS-WebUI/base/nxmc/webapp/,AVAILABLE}{C:\NetXMS-WebUI\webapps\nxmc.war}
2022-10-24 16:48:15.232:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@1725dc0f{/api,file:/C:/NetXMS-WebUI/base/api/webapp/,AVAILABLE}{C:\NetXMS-WebUI\webapps\api.war}
2022-10-24 16:48:15.232:WARN:oejsh.RequestLogHandler:main: !RequestLog
2022-10-24 16:48:15.247:INFO:oejs.ServerConnector:main: Started ServerConnector@3e7e297b{HTTP/1.1}{0.0.0.0:80}
2022-10-24 16:48:15.248:INFO:oejs.Server:main: Started @127700ms

Opening up the webpage however gives me a 404 error:

$ curl -v http://netxms.domain.com
*  Trying 10.1.0.40:80...
* Connected to netxms.domain.com (10.1.0.40) port 80 (#0)
> GET / HTTP/1.1
> Host: netxms.domain.com
> User-Agent: curl/7.83.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 ProxyServlet: /
< Date: Mon, 24 Oct 2022 14:37:18 GMT
< X-Frame-Options: SAMEORIGIN
< Content-Type: text/html; charset=ISO-8859-1
< Cache-Control: must-revalidate,no-cache,no-store
< Content-Length: 296
< Server: Jetty(9.2.19.v20160908)
<
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Error 404 ProxyServlet: /</title>
</head>
<body><h2>HTTP ERROR 404</h2>
<p>Problem accessing /. Reason:
<pre>    ProxyServlet: /</pre></p><hr><i><small>Powered by Jetty://</small></i><hr/>

</body>
</html>
* Connection #0 to host netxms.domain.com left intact

I've also tried the new WebUI (nxmc-4.2.395.war), which loads in seconds instead of minutes, and gives me a working webpage. But when trying to open up a dashboard I get:

and in nxwebui-stderr:

Exception occurred
java.lang.RuntimeException: Failed to register resource: generated/a316538a.png
 at org.eclipse.rap.rwt.internal.resources.ResourceManagerImpl.internalRegister(ResourceManagerImpl.java:146)
[snip because long post]
 ... 41 more

Any ideas on what's going on here?
I also tried using the WebUI installer, which gave me the same 404 error.

Thanks in advance.

]]>https://forum.netxms.org/topic/7538/webui-4.2-http-error-404.-problem-accessing-.RSS for NodeFri, 13 Nov 2026 09:17:43 GMTMon, 24 Oct 2022 15:06:19 GMT60<![CDATA[Reply to WebUI 4.2: HTTP ERROR 404. Problem accessing /. on Wed, 02 Nov 2022 12:42:01 GMT]]>And it works like a charm.  Thank you for solving this so quickly!

]]>https://forum.netxms.org/post/31990https://forum.netxms.org/post/31990Wed, 02 Nov 2022 12:42:01 GMT<![CDATA[Reply to WebUI 4.2: HTTP ERROR 404. Problem accessing /. on Tue, 01 Nov 2022 16:12:07 GMT]]>New Windows installer just published.

Best regards,
Victor

]]>https://forum.netxms.org/post/31981https://forum.netxms.org/post/31981Tue, 01 Nov 2022 16:12:07 GMT<![CDATA[Reply to WebUI 4.2: HTTP ERROR 404. Problem accessing /. on Mon, 31 Oct 2022 14:47:27 GMT]]>Yes, we will update Windows installer.

]]>https://forum.netxms.org/post/31966https://forum.netxms.org/post/31966Mon, 31 Oct 2022 14:47:27 GMT<![CDATA[Reply to WebUI 4.2: HTTP ERROR 404. Problem accessing /. on Thu, 27 Oct 2022 05:58:50 GMT]]>@alk said in WebUI 4.2: HTTP ERROR 404. Problem accessing /.:

Hello.

Since 4.2 web UI require servlet API version 4 (but not version 5!), and jetty9 does not support that. Looks like we forgot to update it in windows installer.

Simplest solution is to install either Jetty10 or Tomcat9 as a standalone product and deploy war file there.

Did you update the Windows installer in the next days, or did I have to use the Jetty or Tomcat alternative for the future?

]]>https://forum.netxms.org/post/31952https://forum.netxms.org/post/31952Thu, 27 Oct 2022 05:58:50 GMT<![CDATA[Reply to WebUI 4.2: HTTP ERROR 404. Problem accessing /. on Fri, 28 Oct 2022 05:56:02 GMT]]>@alk said in WebUI 4.2: HTTP ERROR 404. Problem accessing /.:

Hello.

Since 4.2 web UI require servlet API version 4 (but not version 5!), and jetty9 does not support that. Looks like we forgot to update it in windows installer.

Simplest solution is to install either Jetty10 or Tomcat9 as a standalone product and deploy war file there.

is possible to use Tomcat10 ? or not recommendet/not testing ? on Ubuntu server

]]>https://forum.netxms.org/post/31949https://forum.netxms.org/post/31949Fri, 28 Oct 2022 05:56:02 GMT<![CDATA[Reply to WebUI 4.2: HTTP ERROR 404. Problem accessing /. on Tue, 25 Oct 2022 14:21:12 GMT]]>Yes, this relates both to old and new gui.

]]>https://forum.netxms.org/post/31945https://forum.netxms.org/post/31945Tue, 25 Oct 2022 14:21:12 GMT<![CDATA[Reply to WebUI 4.2: HTTP ERROR 404. Problem accessing /. on Tue, 25 Oct 2022 10:54:47 GMT]]>Also the legacy gui not work, is it the same reason?

]]>https://forum.netxms.org/post/31942https://forum.netxms.org/post/31942Tue, 25 Oct 2022 10:54:47 GMT<![CDATA[Reply to WebUI 4.2: HTTP ERROR 404. Problem accessing /. on Tue, 25 Oct 2022 10:27:14 GMT]]>Hello.

Since 4.2 web UI require servlet API version 4 (but not version 5!), and jetty9 does not support that. Looks like we forgot to update it in windows installer.

Simplest solution is to install either Jetty10 or Tomcat9 as a standalone product and deploy war file there.

]]>https://forum.netxms.org/post/31940https://forum.netxms.org/post/31940Tue, 25 Oct 2022 10:27:14 GMT