Dug up this old thread. In case anybody wondering the same question about
certbot/let's encrypt and web2py.
1. use `--standalone` as David advised. But you have to stop the webserver
everytime you renew.
2. instead, you can use the standard `--webroot` method. Here, you need to
edit your vhost file be it apache or nginx, add a location block:
Using nginx for example:
- location /.well-known {
- root /home/www-data/web2py;
- }
This way, nginx will server the .well-known and skip passing it onto
uwsgi/web2py. Make sure you restart nginx after making this server conf
change and use
sudo certbot certonly/renew --webroot -w /your/path -d example.com -d
www.example.com
On Tuesday, May 30, 2017 at 12:05:01 PM UTC-7, Dave S wrote:
>
>
>
> On Tuesday, May 30, 2017 at 8:50:50 AM UTC-7, Raymond Smith wrote:
>>
>> Please tell me how you did this!! :) IT would be really helpful :)
>>
>>
> I can't answer for the Apache case (or even for the preferred NginX case),
> but I found using CertBot in manual mode was easy (on AWS Linux). Rocket
> was running on port 80, so I told CertBot to use port 443. Whizz bang,
> everything done. I stopped Rocket, restarted it with port 443 and the -c
> and -k arguments (pointing to where CertBot deposited the goods), and
> Poof! It worked!
>
> I still have a Rocket running on port 80, redirecting to https, but will
> probably stop it to run CertBot on port 80 when I need to renew. If I get
> nginx going before then, I'll update this post.
>
> /dps
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
