• Members 14 posts
    Jan. 19, 2025, 8:31 a.m.

    Hi, sorry for my noob question in advance.
    I have a main domain name on which my web application runs (nginx, gunicorn). Now I want to assign a misago forum to a subdomain of my main domain (eg. forum.mysite.com). But when I first configured the misago site, I encountered some errors, in particular conflicts regarding the ports used (because they were already being used by my main application). I tried to modify the docker-compose.yaml file to change the listening ports for my forum, but it doesn't seem to work (I get a misago site error message). I also have errors when ssl certifications for my subdomain. So for the time being, I've deleted my misago containers, and I've come to ask you for help in configuring the subdomain properly.

    Thanks

  • edit

    Thread title has been changed from configuring misago for a subdomain.

  • Jan. 19, 2025, 11:10 p.m.

    Best idea is to run all of it on separate server so there are zero potential conflicts. Alternatively you could create docker-compose.override.yaml file in your misago-docker directory and use it to change ports. Modifying docker-compose.yaml will just cause errors.

    Also, after you modify ports with docker-compose.override.yaml, you will need to setup proxy on your main NGINX instance to proxy subdomain traffic to ports that misago-docker expects.

  • Members 14 posts
    Jan. 23, 2025, 5:33 a.m.

    Hi, @rafalp
    I'm here to report on the port conflict. So I first scanned the ports on which misago was listening, before creating the docker-compose.override.yamlfile. Then I rebuilt and on reverification of the ports, I saw that misago was not only listening on the ports defined in docker-compose.yaml, it was also listening on those defined in docker-compose.override.yaml. Apparently I could specifically prevent the misago process from listening on ports with which it was in conflict, but this seemed tedious. So the short solution I found was to just rewrite in the docker-compose.yaml file to change the listening ports and stop the conflict and it seems to have worked (let me know if it was a bad idea). And then I configured my nginx reverse-proxy to forward requests to misago

  • Members 14 posts
    Jan. 23, 2025, 5:42 a.m.

    There was another problem long before the ports. The lets-encrypt certification. When I had newly configured the site, the message at the end said that ssl/tls certification might take some time to be effective. So I waited about a day but nothing was done (this was before there were conflicts and I configured my nginx file), so since I now had a reverse-proxy I decided to use certbot with my nginx configuration file to obtain certification (tell me if there was another way to solve this problem).

  • Jan. 23, 2025, 9:33 a.m.

    Only problem with your approach is that ./appctl upgrade will now fail on initial git pull because it will see docker-compose.yaml being changed and it will not know how to continue.

    In this situation it would be simpler to create a misago-docker fork that will only differ in using your custom docker-compose.yml. That way ./appctl would pull configuration from your forked repo and there wouldn't be a git conflict. You could even make this fork public seeing how only difference is changed ports and few services removed.

  • Members 14 posts
    Jan. 23, 2025, 3:20 p.m.

    Alright I see. I'm considering the possibility to fork it one day (but it won't be for today lol).
    Anyway, thanks for the support and I won't hesitate to come back if there's anything I need help with.
    By the way is there any command that allows me to completely (I mean really completely) a misago site or misago itself, except deleting the database and the directory ?
    I tried to join the discord but the link seems to have expired. Can I have the new link?

    thanks

  • Jan. 23, 2025, 3:23 p.m.

    Discord link 100% works, new guys are joining with it daily :)

    To completely do what? ;)

  • Members 14 posts
    Jan. 23, 2025, 3:29 p.m.

    Sorry, I meant completely remove

  • Members 14 posts
    Jan. 23, 2025, 3:30 p.m.

    Alright! I retry then

  • Jan. 23, 2025, 5:24 p.m.

    You need to delete docker images, stopped containers and volumes.