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
Using ocap-web with Traefik reverse proxy only works with a root domain or a sub-domain. Trying to use a sub-path (with proxy stripping the /aar prefix so it is even accessible) results in the ocap-web's API calls going to the root domain and as expected hitting a 404.
A config entry for setting the root URL where ocap-web should expect assets/API endpoint to be would solve this issue.
The text was updated successfully, but these errors were encountered:
Sub-path being eg.
example.com/aar
Using ocap-web with Traefik reverse proxy only works with a root domain or a sub-domain. Trying to use a sub-path (with proxy stripping the
/aar
prefix so it is even accessible) results in the ocap-web's API calls going to the root domain and as expected hitting a 404.A config entry for setting the root URL where ocap-web should expect assets/API endpoint to be would solve this issue.
The text was updated successfully, but these errors were encountered: