About the IRC Logs

[Nils Gillmann]

Hi,

first off: sorry that the logs are down for such a long time.

Since someone in your community offered to fix the Apache config,
and I got the okay to share it, you can find the config for the
https://irclogs.gnunet.org appended to this email.

The application running is taking limnoria textfile logs and
publishes them. The sourcecode is https://git.kyriasis.com/kyrias/znc-log-viewer
with some minor modifications (only a local config change).

Because that looks a lot like a TLS handshake, which you most certainly should not be sending to flask.
uwsgi://127.0.0.1:7000/
It's not running under uwsgi, so don't try to proxypass it using the uwsgi protocol.
So either change it to an actual http proxying, or run it under uwsgi.

We are currently busy fighting other fires, but we understand the logs are
important for the hosted communities. If you want to have the current outcome
of a longer discussion displayed, you can help and fix the apache2 config.
The past logs are dumped, they still need to be converted (or the znc-log-viewer
needs some code for SQL).

PS: Please don't use this email to throw discussions about wether your
favorite language or viewer might be the better replacement in my
inbox, there have been discussions and they happened offlist and I'm
not happy with the outcome but it gets the job done.

Thanks, and happy hacking!

[Nils Gillmann]

And here the apache2 config I forgot to append.

Post by Nils Gillmann
Hi,
first off: sorry that the logs are down for such a long time.
Since someone in your community offered to fix the Apache config,
and I got the okay to share it, you can find the config for the
https://irclogs.gnunet.org appended to this email.
The application running is taking limnoria textfile logs and
publishes them. The sourcecode is https://git.kyriasis.com/kyrias/znc-log-viewer
with some minor modifications (only a local config change).

Because that looks a lot like a TLS handshake, which you most certainly should not be sending to flask.
uwsgi://127.0.0.1:7000/
It's not running under uwsgi, so don't try to proxypass it using the uwsgi protocol.
So either change it to an actual http proxying, or run it under uwsgi.

We are currently busy fighting other fires, but we understand the logs are
important for the hosted communities. If you want to have the current outcome
of a longer discussion displayed, you can help and fix the apache2 config.
The past logs are dumped, they still need to be converted (or the znc-log-viewer
needs some code for SQL).
PS: Please don't use this email to throw discussions about wether your
favorite language or viewer might be the better replacement in my
inbox, there have been discussions and they happened offlist and I'm
not happy with the outcome but it gets the job done.
Thanks, and happy hacking!