You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, when I check the logs of the Docker container, I notice that Accent.Endpoint is reported as https://example.com, with the /accent path seemingly removed.
The reported Accent.Endpoint appears to ignore the /accent subpath, potentially causing issues with routing and asset loading.
Steps to Reproduce
Set up Accent behind an Nginx reverse proxy.
Configure the environment variables as shown above.
Check the logs of the Accent Docker container.
Questions
Is there an additional configuration required to properly serve Accent under a subpath?
Am I missing any settings that would allow Accent to respect the CANONICAL_URL and STATIC_URL values fully?
Any guidance would be greatly appreciated. Thanks!
The text was updated successfully, but these errors were encountered:
Description
I am trying to run Accent behind an Nginx reverse proxy. My goal is to make the tool available under a subpath, such as https://example.com/accent.
To achieve this, I have set the following environment variables in my setup:
However, when I check the logs of the Docker container, I notice that
Accent.Endpoint
is reported as https://example.com, with the/accent
path seemingly removed.Expected Behavior
Accent should correctly serve under https://example.com/accent instead of https://example.com.
Actual Behavior
The reported
Accent.Endpoint
appears to ignore the/accent
subpath, potentially causing issues with routing and asset loading.Steps to Reproduce
Set up Accent behind an Nginx reverse proxy.
Configure the environment variables as shown above.
Check the logs of the Accent Docker container.
Questions
Is there an additional configuration required to properly serve Accent under a subpath?
Am I missing any settings that would allow Accent to respect the
CANONICAL_URL
andSTATIC_URL
values fully?Any guidance would be greatly appreciated. Thanks!
The text was updated successfully, but these errors were encountered: