Seq behind YARP Reverse Proxy on /seq Subpath - Static Content 404s #2403
-
|
Hello, I'm trying to put Seq (latest version) behind a YARP reverse proxy on the same server, accessible via the /seq subpath (e.g., http://myserver/seq/). Seq runs internally on http://localhost:5341/. My YARP setup uses a path match for /seq/{**catchAll} and a PathRemovePrefix: "/seq" transform to forward requests to http://localhost:5341/. The initial page loads successfully through YARP. However, static content (CSS, JS) like styles-BZA55ukC.css fails to load with 404 errors. I've configured Seq's api.canonicalUri setting to http://myserver/seq (as suggested for reverse proxy scenarios) and verified Seq loads this setting correctly. Both Seq and YARP have been restarted. Despite setting canonicalUri, the content loading issue persists. How should Seq and YARP be correctly configured to make static content load when accessing Seq via a YARP subpath like /seq/? canonicalUri alone didn't seem to resolve it. Any help appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi @nerusilj, thanks for dropping us a line. Debugging reverse proxy configuration can be quite fiddly, and we're not familiar enough with YARP to provide a definitive answer on this. At first glance, your best chance of success might be adding a response transform targeting If you spot anything we could improve here let me know. Keen to hear how you go! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @nblumhardt Thanks a lot for your response and suggestion regarding the injection via a response transform. After further investigation, I found that while accessing http://srv24/seq results in broken content loading, accessing http://srv24/seq/ works correctly — static resources are resolved properly, and the application behaves as expected. So although adding a response transform in YARP to modify index.html might also work, ensuring the trailing slash (/seq/) is present in the URL has proven to be a sufficient and clean solution for my use case. Thank you again for your time and assistance. |
Beta Was this translation helpful? Give feedback.
Hi @nerusilj, thanks for dropping us a line.
Debugging reverse proxy configuration can be quite fiddly, and we're not familiar enough with YARP to provide a definitive answer on this.
At first glance, your best chance of success might be adding a response transform targeting
index.htmlthat adds<base href="http://myserver/seq/"></base>to the HTML<head>element.If you spot anything we could improve here let me know. Keen to hear how you go!