-
Notifications
You must be signed in to change notification settings - Fork 368
Deployment on CentOS 6.6 #91
Comments
@Jeroen52 camo is designed for Heroku, and on Heroku SSL termination is done before the request hits the application, so camo itself does not know anything about it's own SSL certificates I'm sure it's possible to fork camo and add native SSL support |
You should put a proxy like NGINX in front of it. |
Yeah, I won't accept adding direct SSL to camo. You should use SSL termination like suggested from heroku or a reverse proxy like nginx. |
After working a couple hours this night, I have finally figured out how to run it successfully with the PHPBB plugin thanks to @lenovouser for his suggestion. |
@Jeroen52 I'm glad to hear you got this working. |
@atmos All it took was a couple facepalms and a clear mind and working directory when going into this. For future references on how I got this working on PHPBB 3.1 read phpbb-extensions/camosslimageproxy#3. |
I want to deploy a small instance of Camo on a phpbb 3.1.5 board (which I will soon update to 3.1.6) that is on a CentOS 6.6 dedi, and I am asking if I installed Camo correctly.
I don't think that it has been installed correctly.
Whenever I start Camo I just get this message
SSL-Proxy running on 8081 with pid:31673 version:2.3.0.
Whenever I connect to http://example.com:8081 HSTS automatically redirects me to https://example.com:8081 and Google Chrome gets an ERR_CONNECTION_CLOSED.
Is this normal behaviour?
I also assume that I need a certificate for this, I can get this easily, but where do I need to install the certificate?
The text was updated successfully, but these errors were encountered: