Sinusbot and actual SSL

[olokos]

Hello,

So I have been using sinusbot as https for a while now, but I decided to enable SSL in sinusbot itself aswell

I followed this guide:
https://sinusbot.github.io/docs/reverse-proxy/apache2/
Everything seems to work fine except for some issues

First of all, letsencrypt certificates aren't possible to read by the sinusbot user and prevent it from starting
sinusbot[14286]: error starting up: open /etc/letsencrypt/live/kiepownica.pl/cert.pem: permission denied

As a workaround I have copied all of those to /opt/sinusbot/somefolder but I don't think it's the right solution, or is it?
Definitely better than setting the entire /etc/letsencrypt as 755 if you ask me.

Whenever I enable UseSSL=true the server gives out error 502 Proxy error
and the sinusbot has this error in logs
sinusbot[19463]: echo: http: TLS handshake error from 127.0.0.1:59320: tls: first record does not look like a TLS handshake


I've seen this thread about the issue https://forum.sinusbot.com/threads/ssl-for-the-bot.1263/
But it doesn't provide an actual solution, or I have just missed it somehow.

Additionally, shouldn't we use Redirect / https://sbot.yourdomain.com instead of the RewriteEngine for port 80? Seems to be cleaner that way.

 

[Multivitamin]

You need to either decide if you use the built in ssl module or one from apache, if you follow the apache guide then the sinusbot user will never need to be able to read the certificate

So just deactivate the ssl stuff in the config.ini and just use it via apache

 

[olokos]

You need to either decide if you use the built in ssl module or one from apache, if you follow the apache guide then the sinusbot user will never need to be able to read the certificate

So just deactivate the ssl stuff in the config.ini and just use it via apache

So basically the functionality of SSL in the sinusbot works exactly the same as if I configure the apache2 to serve the panel via https?

I already had that using apache2, but I was wondering if setting up SSL within sinusbot is any safer or better from using just the apache2 configuration only, so I tried to make it SSL both within sinusbot and apache2.

If I get this correctly, it's either SSL in sinusbot or in apache2 and it cannot be both?
@Multivitamin

 

[olokos]

Bumpy @Multivitamin
I'd really appreciate a definitive answer, whether just hosting sinusbot via apache2 proxy and https is enough or can I also add SSL within sinusbot on top of that?

 

[flyth]

If I get this correctly, it's either

You could run both with SSL, but if both services are running on the same machine, there's absolutely no benefit in doing that.