and ill i get is service "web" is not running. i can get to the port with login page though
Originally created by @reitenth on GitHub (Feb 5, 2025).
ive tried running `docker compose exec -it web python manage.py createsuperuser`
and ill i get is `service "web" is not running.` i can get to the port with login page though
adam
added the question label 2025-12-28 23:24:16 +01:00
Make sure replace wygiwyh_server with your actual WYGIWYH container name (not the postgres one), the default shoud be wygiwyh_server.
If you still have problems, could you share your docker-compose.yml file? Let me know how it goes.
@eitchtee commented on GitHub (Feb 5, 2025):
If you've renamed the `web` service you need to replace `web` in the command with the name you used. For example:
```yaml
services:
web: <---- see if this is called web, if it isn't replace web in the command with the name that's here
image: eitchtee/wygiwyh:latest
```
Alternatively you can use:
`docker exec -it wygiwyh_server python manage.py createsuperuser`
Make sure replace `wygiwyh_server` with your actual WYGIWYH container name (not the postgres one), the default shoud be `wygiwyh_server`.
If you still have problems, could you share your docker-compose.yml file? Let me know how it goes.
@eitchtee commented on GitHub (Feb 5, 2025):
So, I managed to reproduce this using your docker-compose.
The problem seems to be related to `network_mode: bridge`, assuming you're using the default env variables.
The default bridge doesn't provide name resolution to containers, so the app can't communicate with your postgres instance over the container name, so you'll need to provide an IP address on the SQL_HOST env variable or, the better option, provide a user-defined network. See https://github.com/docker/compose/issues/9513 and https://stackoverflow.com/a/52418815 and https://docs.docker.com/engine/network/drivers/bridge/#differences-between-user-defined-bridges-and-the-default-bridge
Also, did you manage to create the superuser or you still can't and everything else is happening together.
@eitchtee commented on GitHub (Feb 5, 2025):
Also, did you manage to create the superuser or you still can't and everything else is happening together.
@reitenth commented on GitHub (Feb 5, 2025):
tried with a custom network still not working.
<img width="703" alt="Image" src="https://github.com/user-attachments/assets/293c5e8b-eee3-4452-8831-dd11e47c7d98" />
<img width="887" alt="Image" src="https://github.com/user-attachments/assets/cf39e074-8a50-4e11-991d-2d1d516f893c" />
The logs seem fine, no mention of the errors you mentioned previously, is it restarting infinitely or something? What isn't working?
@eitchtee commented on GitHub (Feb 5, 2025):
The logs seem fine, no mention of the errors you mentioned previously, is it restarting infinitely or something? What isn't working?
Do you have anymore log lines after the ones you showed?
Try adding a DJANGO_ALLOWED_HOSTS env variable with a value of *.
@eitchtee commented on GitHub (Feb 5, 2025):
Do you have anymore log lines after the ones you showed?
Try adding a `DJANGO_ALLOWED_HOSTS` env variable with a value of `*`.
I managed to setup UnRaid on a VM just to test things out, as I've never used it. I managed to get it working on the bridge network, below are my configurations:
The SQL_HOST is the IP of the postgres instance
One thing I found out, and it might be what's happening to you, is that if I click the WebUI button on the UnRaid UI, it redirects me to an https:// link, which obviously won't work and gave me a This site can’t be reached error, simply changing it to http:// did the trick.
Finally, for future reference, for a easier user creation in UnRaid just click WYGIWYH container name on UnRaid, choose Console, then type python manage.py createsuperuser on the screen that will open.
@eitchtee commented on GitHub (Feb 5, 2025):
Your logs and configs looks good.
I managed to setup UnRaid on a VM just to test things out, as I've never used it. I managed to get it working on the bridge network, below are my configurations:


The SQL_HOST is the IP of the postgres instance

---
One thing I found out, and it might be what's happening to you, is that if I click the WebUI button on the UnRaid UI, it redirects me to an `https://` link, which obviously won't work and gave me a This site can’t be reached error, simply changing it to `http://` did the trick.


---
Finally, for future reference, for a easier user creation in UnRaid just click WYGIWYH container name on UnRaid, choose Console, then type `python manage.py createsuperuser` on the screen that will open.
If the problem persists, it's outside my league, and you'll need to tinker with your network settings to see what works.
Since you're getting a generic This site can’t be reached error from your browser, it's probably a network issue, i.e. the IP you're trying to access it with is not the IP you should be accessing, etc.
@eitchtee commented on GitHub (Feb 5, 2025):
If the problem persists, it's outside my league, and you'll need to tinker with your network settings to see what works.
Since you're getting a generic This site can’t be reached error from your browser, it's probably a network issue, i.e. the IP you're trying to access it with is not the IP you should be accessing, etc.
thanks for the help, i went over everything in your file and it was indeed the https. the template in unraid has it in the advanced web ui settings instead of http. i created a superuser as well with that command. thanks
@reitenth commented on GitHub (Feb 5, 2025):
thanks for the help, i went over everything in your file and it was indeed the https. the template in unraid has it in the advanced web ui settings instead of http. i created a superuser as well with that command. thanks
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @reitenth on GitHub (Feb 5, 2025).
ive tried running
docker compose exec -it web python manage.py createsuperuserand ill i get is
service "web" is not running.i can get to the port with login page though@eitchtee commented on GitHub (Feb 5, 2025):
If you've renamed the
webservice you need to replacewebin the command with the name you used. For example:Alternatively you can use:
docker exec -it wygiwyh_server python manage.py createsuperuserMake sure replace
wygiwyh_serverwith your actual WYGIWYH container name (not the postgres one), the default shoud bewygiwyh_server.If you still have problems, could you share your docker-compose.yml file? Let me know how it goes.
@reitenth commented on GitHub (Feb 5, 2025):
ok im having an issue starting the container now
keep getting
error connecting in 'pool-1': [Errno -2] Name or service not known@reitenth commented on GitHub (Feb 5, 2025):
the logs get stuck at this line a lot
[17] [INFO] Booting worker with pid: 17@eitchtee commented on GitHub (Feb 5, 2025):
So, I managed to reproduce this using your docker-compose.
The problem seems to be related to
network_mode: bridge, assuming you're using the default env variables.The default bridge doesn't provide name resolution to containers, so the app can't communicate with your postgres instance over the container name, so you'll need to provide an IP address on the SQL_HOST env variable or, the better option, provide a user-defined network. See https://github.com/docker/compose/issues/9513 and https://stackoverflow.com/a/52418815 and https://docs.docker.com/engine/network/drivers/bridge/#differences-between-user-defined-bridges-and-the-default-bridge
@eitchtee commented on GitHub (Feb 5, 2025):
Also, did you manage to create the superuser or you still can't and everything else is happening together.
@reitenth commented on GitHub (Feb 5, 2025):
tried with a custom network still not working.
@eitchtee commented on GitHub (Feb 5, 2025):
The logs seem fine, no mention of the errors you mentioned previously, is it restarting infinitely or something? What isn't working?
@reitenth commented on GitHub (Feb 5, 2025):
the webui wont load
This site can’t be reached@eitchtee commented on GitHub (Feb 5, 2025):
Do you have anymore log lines after the ones you showed?
Try adding a
DJANGO_ALLOWED_HOSTSenv variable with a value of*.@reitenth commented on GitHub (Feb 5, 2025):
already had allowed hosts to my ip.
@eitchtee commented on GitHub (Feb 5, 2025):
Your logs and configs looks good.
I managed to setup UnRaid on a VM just to test things out, as I've never used it. I managed to get it working on the bridge network, below are my configurations:
The SQL_HOST is the IP of the postgres instance
One thing I found out, and it might be what's happening to you, is that if I click the WebUI button on the UnRaid UI, it redirects me to an
https://link, which obviously won't work and gave me a This site can’t be reached error, simply changing it tohttp://did the trick.Finally, for future reference, for a easier user creation in UnRaid just click WYGIWYH container name on UnRaid, choose Console, then type
python manage.py createsuperuseron the screen that will open.@eitchtee commented on GitHub (Feb 5, 2025):
If the problem persists, it's outside my league, and you'll need to tinker with your network settings to see what works.
Since you're getting a generic This site can’t be reached error from your browser, it's probably a network issue, i.e. the IP you're trying to access it with is not the IP you should be accessing, etc.
@reitenth commented on GitHub (Feb 5, 2025):
thanks for the help, i went over everything in your file and it was indeed the https. the template in unraid has it in the advanced web ui settings instead of http. i created a superuser as well with that command. thanks
@eitchtee commented on GitHub (Feb 5, 2025):
All good. Hope you like the app.