Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nginx reverse proxy setup - font problem #3861

Closed
m4r2 opened this issue Oct 29, 2024 · 1 comment · Fixed by #3862
Closed

Nginx reverse proxy setup - font problem #3861

m4r2 opened this issue Oct 29, 2024 · 1 comment · Fixed by #3862

Comments

@m4r2
Copy link

m4r2 commented Oct 29, 2024

I deployed the Velociraptor server behind a Nginx reverse proxy and I have the problem, that the fonts can't be loaded.
I have used the Nginx configuration as described in that article: https://docs.velociraptor.app/blog/2020/2020-09-28-velociraptor-network-communications-30568624043a/

In the console of the browser I've found these errors, that iosevka-term-medium-subset-d289edc8.woff2 can't be loaded:
image
As you can see in the screenshot, the domain is missing in the link. This causes the GUI to become slow and a standard font is used.
image
An other problem (maybe related) is, when I request https:///gui, the gui loads but it redirects the browser to https:///app. When I do reload I get an error 404, because the reverse proxy config does not include /app.

I use Velociraptor 0.73.2.

@scudette
Copy link
Contributor

This is probably related to, or a duplicate of #3859 . I think the loading of the fonts is not actually easy to solve - we have seen it before here https://discord.com/channels/624244632552734750/624244632552734752/1270545691260883059

scudette added a commit that referenced this issue Oct 30, 2024
Various internal links were broken when a base path was specified.

Fixes: #3861
scudette added a commit that referenced this issue Oct 30, 2024
Various internal links were broken when a base path was specified.

Fixes: #3861
scudette added a commit that referenced this issue Nov 4, 2024
Various internal links were broken when a base path was specified.

Fixes: #3861
scudette added a commit that referenced this issue Nov 4, 2024
Various internal links were broken when a base path was specified.

Fixes: #3861
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants