In the Regions list click Add and enter: Name: nyc1.
In the Providers list click Add and enter DigitalOcean. Choose Edit > Settings > Transfers > S3 Providers. (Yes I've attempted with the direct IP as well)Į: I'm updating today from v0.9.8.1 Release Build and I'll try again. In order to connect to DigitalOcean Spaces follow the steps described below. I've attempted to locate the log itself but on my instance it returns a file not foundīut from trying the web container logs it doesn't provide a valid response. The SFTPgo log itself (from the host, docker-compose exec -user=azuracast web tail -f ~/sftpgo/sftpgo.log)Ĭheck both of these logs as you're trying to connect to see if there's any obvious answer as to why it's not connecting.The main web container log (from the host, docker-compose logs -f web).In order for me to more accurately diagnose what's going on, there are two logs that could be checked: I'm unfortunately unable to reproduce this error locally on my local installation, sftp works without any issues at all and successfully authenticates. There were a number of technical reasons why we switched away from FTP to SFTP, which we outlined in the 0.9.8.1 release notes and elsewhere online, and those issues are still valid. We are not planning to go back to supporting FTP.
0 kommentar(er)
