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
run docker (with and without sudo, its the same result) docker compose up -d
Currently I cannot access the website under http://butch:81
I am always redirected (by the browser) to https. When I use the incognito mode, it does not do this. But I always get ‘The website is not available’
the log file from the docker still contains the message.
Folder /mediawiki contains
important data and must be mounted to persistent storage!
+ case $1 in
+ return 1
+ exit 1
I can't assign it at the moment, but the folders are created correctly when the docker is started.
Steps to reproduce the issue (if applicable):
clone repro
modify .env (see above)
run docker (see above)
navigate ro butch:81
Expected behavior
webpage should display the wiki
System info
Canasta version: Latest
Canasta CLI version : Latest
Host operating system: Debian bookworm
Do you have sudo/root permissions on the host OS?: yes
The text was updated successfully, but these errors were encountered:
Disable caddy using docker-compose.override.yml to stop redirection to https.
For the error which you saw in logs, please mount an empty directory to /mediawiki using docker-compose.override.yml
Describe the situation
Description:
I have configured the environment as follows - I have solved the problem with Elasticsearch (see other ticket) by commenting it out.
.env
run docker (with and without sudo, its the same result)
docker compose up -d
Currently I cannot access the website under
http://butch:81
I am always redirected (by the browser) to https. When I use the incognito mode, it does not do this. But I always get ‘The website is not available’
the log file from the docker still contains the message.
Steps to reproduce the issue (if applicable):
Expected behavior
webpage should display the wiki
System info
The text was updated successfully, but these errors were encountered: