499 reported in nginx reverse proxy #834
-
HTTP code 499 usually is seen in NGINX's logs. Being a web server, NGINX 499 is able to identify that the problem is not in the server itself, or the entity which sent the request. HTTP error 499 simply means that the client shut off in the middle of processing the request through the server. When requesting home page of admin UI, main index is loaded, but resources not, e.g. It works when I requesting the original IP with port. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
I'm not sure what could cause this. As you quoted, 499 is usually returned for example on client-side timeouts (the 504 also seems to confirm it), but I'm not sure why. Since it works when accessing it with the IP, then most likely it is misconfiguration of the nginx proxy. Could you post here your nginx config or try the example one from https://pocketbase.io/docs/going-to-production/#deploy-behind-reverse-proxy. I'll move the issue to Q&A discussion. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, sorry for not finding this helpful section, it's some misconfiguration in my nginx proxy, the example works! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @wizicer can you share your problem? I got 499 too :(, and I don't know how to fix it |
Beta Was this translation helpful? Give feedback.
-
|
Hi @tinguyen1107 , I forget the details. However, I remember I just follow the steps in above link exactly and it works then. |
Beta Was this translation helpful? Give feedback.
I'm not sure what could cause this. As you quoted, 499 is usually returned for example on client-side timeouts (the 504 also seems to confirm it), but I'm not sure why.
Since it works when accessing it with the IP, then most likely it is misconfiguration of the nginx proxy. Could you post here your nginx config or try the example one from https://pocketbase.io/docs/going-to-production/#deploy-behind-reverse-proxy.
I'll move the issue to Q&A discussion.