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
I need to get baikal working from behind an apache reverse-proxy server.
Many docker apps contain a base_uri parameter that can easily allow this to work by creating a subdomain: http://localhost/baikal. Although baikal does have a base_uri subdomain field, it does not work with this image.
I set the base_uri '' to base_uri '/baikal', base_uri 'baikal', base_uri 'baikal/' etc. and none of them work. They all just end up breaking the admin page and then the baikal logs show these errors:
49#49 *1 /var/www/baikal/html/index.php is not found (2: no such file or directory), client: ip, server: , request: "GET /baikal/ HTTP/1.1, host, referet etc. Then I see the 404 message "GET /baikal/
51#51: *3 FastCGI send in stderr: "PHP message: LogicException: Request uri (/dav.php/calendars/users/default) is out of the base uri (baikal/dav.php/) in /var/www/baikal/vendor/sabre/http/lib/Request
...etc
So my first question is, how is this even supposed to work, setting the base_uri parameter after the file is created doesn't seem to do anything internally, is it supposed to work or is this just a placeholder for future configuration?
I also tried another approach to this issue, I tried stripping out the subdomain with apache. For example, I am migrating from the radicale docker image. It is well documented and they provide this code which works to do this for radicale. I modified it for baikal:
RewriteEngine On
RewriteRule ^/baikal$ /baikal/ [R,L]
<Location "/baikal/">
ProxyPass http://localhost:1234/
ProxyPassReverse http://localhost:1234/
RequestHeader set X-Script-Name /baikal
</Location>
It does not work however, all the images and page links are broken and still referring to the original url, after loading the admin login page and clicking submit you get a 404 error.
I can see many of the issues and discussions here are of users trying to get this docker image to work on a server behind reverse proxy. Has anyone successfully got the project to work behind an apache? Even putting aside the proxy and loading the page locally: 'http://localhost/baikai' does not work either, is it supposed to work or do each one of the systems inside the docker image also need to be configured?
The text was updated successfully, but these errors were encountered:
I need to get baikal working from behind an apache reverse-proxy server.
Many docker apps contain a base_uri parameter that can easily allow this to work by creating a subdomain:
http://localhost/baikal.
Although baikal does have a base_uri subdomain field, it does not work with this image.I set the base_uri '' to
base_uri '/baikal'
,base_uri 'baikal'
,base_uri 'baikal/'
etc. and none of them work. They all just end up breaking the admin page and then the baikal logs show these errors:So my first question is, how is this even supposed to work, setting the base_uri parameter after the file is created doesn't seem to do anything internally, is it supposed to work or is this just a placeholder for future configuration?
I also tried another approach to this issue, I tried stripping out the subdomain with apache. For example, I am migrating from the radicale docker image. It is well documented and they provide this code which works to do this for radicale. I modified it for baikal:
It does not work however, all the images and page links are broken and still referring to the original url, after loading the admin login page and clicking submit you get a 404 error.
I can see many of the issues and discussions here are of users trying to get this docker image to work on a server behind reverse proxy. Has anyone successfully got the project to work behind an apache? Even putting aside the proxy and loading the page locally: 'http://localhost/baikai' does not work either, is it supposed to work or do each one of the systems inside the docker image also need to be configured?
The text was updated successfully, but these errors were encountered: