Created
July 19, 2013 10:16
-
-
Save Eugeny/6038158 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Debugging stunnel problems in Ajenti: | |
0. Disable SSL in ajenti: | |
change "ssl": { "enable": true to false in /etc/ajenti/config.json | |
service ajenti restart | |
1. Regenerate the certificate | |
ajenti-ssl-gen hostname -f | |
2. Create following config file /tmp/stunnel.conf | |
cert = /etc/ajenti/ajenti.pem | |
foreground = yes | |
pid = | |
[default] | |
accept = 0.0.0.0:8001 | |
connect = 127.0.0.1:8000 | |
3. Start stunnel: | |
stunnel /tmp/stunnel.conf | |
4. Check for errors; you should be able to access Ajenti through https://<ip>:8001 | |
Please let me know if you get any errors on any of these steps. |
In case you never figured this out, I was facing the exact same problem but turns out I was only experiencing this issue behind my company's firewall.. https:// works like a charm outside the office.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I get no errors but I still cannot access the panel through https://:8001 or https://:8000 however I can access the application by using http protocol and get a Insecure communication Your credentials will be transmitted in plain text! error /warning