@thomthom my backups are running again. Ottomatik solved it

Hello, thank you for that information - we have deployed a new update that has now fixed this issue up. I will continue to monitor things to ensure everything is working.

Hello, Kevin here from the Ottomatik team - it looks like PIP v10.0.0 had caused a different output to be displayed, which broke our regex. This has now been fixed up and everything should be functional again.

I do apologize for the inconvenience.

If anyone is still having issues please feel free to contact us.

Ah, LetEncrypt was something I had only enabled on the new server. Explains why the old remained the same.

I got to say, updating major versions of a package like that isn't a great thing to do. That should be left to the owner of the server. And if a newer version would be needed the owner should be notified and given the option to control the upgrade.

This is why I'm not buying into the "always on the latest and greatest". There is always some compatibility friction with that.

For anyone wondering about this, the letsencrypt client required a pip upgrade so it can install the required dependencies to issue new certificate or renew existing ones.

So if any of your certificates were renewed or a new certificate was issues, pip was updated.

I just got confirmation from Forge support on this. I responded with a request to be more conservative in upgrading packages - avoiding automatically updating major versions due to potential breaking changes.

On one server PIP was broken after this (so Ottomatik still failed), I got this error when running pip -V:

Traceback (most recent call last):
  File "/usr/local/bin/pip", line 7, in <module>
    from pip._internal import main
ImportError: No module named _internal

I had to run:

#remove pip
sudo apt-get remove python-pip python-dev

#install pip via python
curl https://bootstrap.pypa.io/get-pip.py | sudo python

To install pip correctly. After this Ottomatik worked. See this thread for reference

@adaptivemedia If you haven't done so already, I'd recommend you mention this to Forge support. And suggest that updating major package versions automatically without notice isn't ideal. I already mentioned it - though I didn't get any response to that.