• Members 2 posts
    Sept. 2, 2020, 6:41 a.m.

    Before I install Misago, there are a few things to explain about my server:
    1.some info about version:
    os version : CentOS Linux release 7.8.2003 (Core) ;
    core version: 3.10.0-957.10.1.el7.x86_64;
    docker version: Docker version 19.03.12, build 48a66213fe;
    docker-compose version 1.24.1, build 4667896b;
    2.Nginx already exists on my server, and ports 80 and 443 have been used, and I cannot stop these services temporarily.

    Based on the above situation,I modified the port number of the "nginx-proxy" service in the "docker-compose.yaml" file and performed misago-docker. After that, I did a "proxy_pass" forwarding on the "nginx" service on my server.Then,I added a " my domain" message to my server's hosts file so that I can access my newly built Misago site normally.

    However, I encountered a new problem when logging in:
    "Your request was rejected because your browser didn't send the CSRF cookie, or the cookie sent was invalid."

    I can’t find "misagocsrftoken" in Cookie, Request, or page.Could you please provide me with ideas for solving this problem? thank you very much!

  • Sept. 3, 2020, 12:40 a.m.

    Marked as best answer by Jan. 15, 2023, 2:57 a.m..

    misago-docker is configured for production deployments. It requires HTTPS to work, and this will not work on localhost.

    If you wish to just play with Misago on localhost, please try main repo instead.

  • Members 2 posts
    Sept. 3, 2020, 4:38 a.m.

    You are right, when my domain name has HTTPS, misago-docker can run normally on my production server. Thank you very much, your work is very good, you are my role model!