Weblate transient errors

Bonjour,

Because of how https is implemented the crontab that updates can incorrectly capture and invalidate some HTTP requests. It is mistaken to have an environment. I implemented a workaround by commenting out the offending variables

#            - VIRTUAL_HOST=weblate.securedrop.club                                                                                                                                                            
#            - LETSENCRYPT_HOST=weblate.securedrop.club                                                                                                                                                        
#            - LETSENCRYPT_EMAIL=admin@securedrop.club                                                                                                                                                         

in the weblate-docker/docker-compose.override.yml. They are already set in the desired container and won’t be set by the process run via the crontab. The errors won’t bother us anymore.

The better solution is to switch to the method the upstream chose: it is better for maintenance.

Cheers

The above solution had the inconvenient that it needs to be reverted when restarting the weblate container. Instead the crontab can be changed to override the variables that get the nginx proxy confused:

*/5 * * * * cd /home/ubuntu/weblate-docker; sudo docker-compose run -e VIRTUAL_HOST=none -e LETSENCRYPT_HOST=none --rm weblate update_index
@daily cd /home/ubuntu/weblate-docker; sudo docker-compose run -e VIRTUAL_HOST=none -e LETSENCRYPT_HOST=none --rm weblate cleanuptrans
@hourly cd /home/ubuntu/weblate-docker; sudo docker-compose run -e VIRTUAL_HOST=none -e LETSENCRYPT_HOST=none --rm weblate commit_pending --all --age=1