Blame
| db6892 | Anonymous | 2026-04-13 07:02:27 | 1 | # Setup Certificates for a New URL |
| 2 | ||||
| 3 | 1. SSH into INDRA (where the URL points to) |
|||
| 4 | ||||
| 5 | 2. Run `sudo certbot --nginx -d $YOUR_URL` |
|||
| 6 | ||||
| 7 | ## Renew Certificates for a New URL |
|||
| 8 | ||||
| 9 | This should not be necessary, as modern installations set up a cron job |
|||
| 10 | to do this twice daily. |
|||
| 11 | ||||
| 12 | In case you have to do this manually: |
|||
| 13 | ||||
| 14 | 1. SSH into INDRA (where the URL points to) |
|||
| 15 | ||||
| 16 | 2. Run `sudo certbot renew` (you can add `--dry-run` to simulate it |
|||
| 17 | without persisting changes) |
|||
| 18 | ||||
| 19 | ## Why INDRA? |
|||
| 20 | ||||
| 21 | The URL [gitea.dev.isn.edu.au](https://gitea.dev.isn.edu.au) points to |
|||
| 22 | INDRA, where *nginx* is configured to proxy requests to our TrueNAS |
|||
| 23 | host, which runs Gitea as a managed application. |