Can one deactivate Let's Encrypt and let misago run only via http? So that one can then use a reverse proxy externally
-
-
AFAIR simplest way to achieve that is to create fork of
misago-dockerthat deletesnginx-lets-encryptfromdocker-compose.ymlfile. -
-
Actually, you can delete both
nginx-lets-encryptandnginx-proxyand add this entry tomisagoservice:ports: - "3031:3031"Now you need to setup your proxy to:
- Serve
mediadirectory under/media/path - Serve
staticdirectory under/static/path - Proxy rest of requests to
localhost:3031
- Serve
-
How? I have this:
<VirtualHost *:80> ServerName ADRESS ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined RewriteEngine on RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] </VirtualHost> <VirtualHost *:443> ServerName ADRESS ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined SSLEngine On SSLCertificateFile /etc/letsencrypt/live/ADRESS/cert.pem SSLCertificateKeyFile /etc/letsencrypt/live/ADRESS/privkey.pem SSLCertificateChainFile /etc/letsencrypt/live/ADRESS/fullchain.pem ProxyPass / http://127.0.0.1:3031/ ProxyPassReverse / http://127.0.0.1:3031/ </VirtualHost> -
Please stop tagging me.
I don’t know what you are supposed to do next with that config, I am not fimiliar with Apache.
If you are trying to do custom setup, you should have knowledge of technologies you are going to use. Maybe other user on this forum will have a knowledge of Apache and will be able to help?
-
Well, Misago itself can't be reached on port 3031 either
-
Or rather... The connection is always interrupted
-
I'd like to refrain from pinging you, but... Where are you? It always says you're online
-
@Justman10000 this is final warning. You either understand that this is an open source software and I am only helping people out of good will and I am unable to spend time helping people researching their custom setups, or we can part ways.
-
You told me that, so surely you know why Misago doesn't work?
-
If its Misago thats not working, can you show an error from it?
-
That's the strange thing, no errors are logged
-
What is not working then? Is misago docker not starting?
-
The Docker container is active, but when I call the URL, this comes up:
-
Have you verified that your configuration is correct and the problem is with Misago docker, eg. by running different app using your apache config?
-
You might want to look at Install misago in a podman pod under linux which uses the misago container image.
While the instructions are for podman, it is an approach that is equally applicable in docker, or k8s.
This is not an officially supported method, and is provided on a best effort basis.
As is the misago official docker deployment.
Support might be politely asked for, but should not be demanded, nor expected.
-
I ventured deeper into the system! The only log entry that repeats when I try to call Misato is this one:
invalid request block size: 21573 (max 4096)...skip
