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
Configure the Wallabag installation using docker-compose.yml with the environment variable SYMFONY__ENV__DOMAIN_NAME=https://YOUR_DOMAIN/wallabag
Configure the reverse proxy (e.g. Traefik) to route the above URL to the Wallabag container
Make sure the reverse proxy removes the path prefix (for Traefik: use the stripprefix middleware)
Start the necessary containers
Navigate to https://YOUR_DOMAIN/wallabag
This will already fail because Wallabag redirects to /login, not honoring the subpath in the domain_name setting
Workaround: Navigate to https://YOUR_DOMAIN/wallabag/login to circumvent the erroneous redirect
Some resources will not be loaded correctly since the links used to load them are relative, not honoring the path.
Try to log in using the configured default credentials. This will fail again because Wallabag will redirect to the relative link /login_check, also not honoring the subpath.
This screenshot of the source code for https://YOUR_DOMAIN/wallabag/login shows one wrong link alongside some correct links:
At the bottom of the file there are some non-functional relative links:
The text was updated successfully, but these errors were encountered:
When using a subpath in DOMAIN_NAME, e.g. https://my.domain.com/wallabag, the subpath /wallabag is sometimes honored, sometimes not.
See the attached screenshot of the login page source for an example.
Environment
My
app/config/parameters.yml
is:What steps will reproduce the bug?
docker-compose.yml
with the environment variableSYMFONY__ENV__DOMAIN_NAME=https://YOUR_DOMAIN/wallabag
stripprefix
middleware)domain_name
settingThis screenshot of the source code for https://YOUR_DOMAIN/wallabag/login shows one wrong link alongside some correct links:
At the bottom of the file there are some non-functional relative links:
The text was updated successfully, but these errors were encountered: