Rest call Failed (HTTP 401) error #1272
-
|
I have an Nzyme server running 2.0.0-alpha.17. I am consistently getting REST call failed (HTTP 401) error while actively using the web console. Looking at the nzyme log the error below is the only 1 I am seeing. Anyone have an idea of what could be the issue or where I could continue troubleshooting at? 2025-05-23T18:21:57.331+0000 [grizzly-http-server-3] ERROR org.glassfish.jersey.server.ServerRuntime$Responder - An I/O error has occurred while writing a response message entity to the container output stream. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 13 replies
-
|
Is there anything sitting between your browser and the API? Load balancer, reverse proxy, WAF, Cloudflare, etc? |
Beta Was this translation helpful? Give feedback.
-
|
The Nzyme server is behind a pfSense firewall that has a Tailscale VPN & is NATing for the LAN. I am connecting into that LAN via the VPN. This setup is also at a second location and is not currently having the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
OK! Thanks! Check if any of that causes packet loss. Do you get logged out when the error occurs? Do some pages work and some don't? Can you check if all your clocks on your client and Nzyme infrastructure are synchronized? |
Beta Was this translation helpful? Give feedback.
-
|
Dont appear to have any packet loss. Every page works before the error occurs and no page appears to specifically cause it to happen. A majority of the time it will log me out and bring me back to the login page. Occasionally it will error and not automatically redirect me to the login page but brings me there when I try to navigate to any other page on Nzyme. Times are sync'd between the taps, server, and my endpoint. |
Beta Was this translation helpful? Give feedback.
-
|
OK! Thanks! Can you post the full |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
heap size was still default of 1GB. Changed it to Xms=4 and Xmx=8. Error still appears to be happening. |
Beta Was this translation helpful? Give feedback.
-
|
Can you try to see if you get that |
Beta Was this translation helpful? Give feedback.
-
|
The Error is occurring each time the logout is. 2025-05-26T15:12:50.727+0000 [grizzly-http-server-10] INFO app.nzyme.core.rest.resources.system.authentication.AuthenticationResource - Creating session for user [[email protected]] 2025-05-26T15:20:31.964+0000 [grizzly-http-server-12] INFO app.nzyme.core.rest.resources.system.authentication.AuthenticationResource - Creating session for user [[email protected]] 2025-05-26T15:27:46.884+0000 [grizzly-http-server-1] INFO app.nzyme.core.rest.resources.system.authentication.AuthenticationResource - Creating session for user [[email protected]] |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thanks! I looked into the cause of these exceptions one more time and it's definitely your client (or something in between) closing the connection during the servers response handling. Does the web interface feel sluggish and slow before you are logged out? This is either a load or a network issue. You could try without Tailscale. A PCAP may help diagnose this, too. |
Beta Was this translation helpful? Give feedback.
-
|
I will continue testing in the future, moving lab environments now. The internet connection out was through cellular on the Nzyme server side, so it is possible it was dropping packets unexpectedly and I just did not see it on my end. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, trying to push this through a mobile connection will likely cause this. |
Beta Was this translation helpful? Give feedback.
Ok, thanks! I looked into the cause of these exceptions one more time and it's definitely your client (or something in between) closing the connection during the servers response handling.
Does the web interface feel sluggish and slow before you are logged out? This is either a load or a network issue. You could try without Tailscale. A PCAP may help diagnose this, too.