1and1 FTP is unreliable

[chuckwagoncomputing]

We keep getting errors like this, which leaves things broken.

connect failed: Connection refused.
connect failed: Connection refused.
connect failed: Connection refused.
Falling back to PORT instead of PASV mode.
pinouts/proteus/white35.jpg:    Lost data connection to remote host after 32768 bytes had been sent: Broken pipe.

[rusefillc]

We now have https://rusefi.com/docs/pinouts-backup/ one time manual backup

in my opinion we need to push pinout pages into git. those are kind of same thing-ish as .ini files?

also it would be a dream to have a .pdf generated automatically

[rusefillc]

https://stackoverflow.com/questions/24763742/lftp-reconnect-infinite-loop

[rusefillc]

Root cause: 1and1 does not provide us with a reliable FTP which is not horrible by itself. what's horrible is the fact that 1and1 is unreliable specifically in a way where we kill old version of the page while do not create new one

for pinouts and build artifacts I suggest we move to github pages

#170

[chuckwagoncomputing]

I'm worried about git drama with multiple workflows trying to push to GH Pages. I'm too tired right now to actually think it through though.

Another part of this problem is that we are transferring many files, multiplying the chances for failure. If 1and1 had ssh access we could solve that particular issue.

[rusefillc]

Well technically 1and1 has ssh - primary account is ssh-enabled

[chuckwagoncomputing]

OK, so using the primary account would mean putting the authentication details or a private key in GH Secrets. Preferably a private key used only for this.

[chuckwagoncomputing]

Preferably a private key used only for this.

This is so it can be deleted to remove access in case it gets out.
And you can keep your own password or key and change it as you please, without having to update Github.

[chuckwagoncomputing]

Are you ready to switch to SSH?
If so, I need the path the files need to go to; e.g. /var/www/docs

[rusefillc]

huh? why would anything change with paths?

in rusefi/rusefi@471a2ef it seemed like we only replace the command while all paths stay the same?

[chuckwagoncomputing]

I'm not sure how you've had FTP set up, but typically FTP is scoped to a specific directory, and the rest of the file system is inaccessible. With SSH, if you don't cd somewhere, files will by go in the home directory. Have you confirmed that the files were indeed updated on the server?

[rusefillc]

I cannot explain it but yes looks like files are updating

[chuckwagoncomputing]

That just shows that the file has been successfully uploaded. That does not mean that it has been uploaded to the correct path. What is the HTTP URL this is hosted at?

[rusefillc]

https://rusefi.com/build_server/autoupdate/

[rusefillc]

and https://rusefi.com/build_server/

[chuckwagoncomputing]

Oh yes, I was being dumb and didn't see that file. It does look like it's working properly, which means files are just in the home directory. That question being cleared up, I can get to work on switching to SSH. Thanks.

[rusefillc]

broken again :( https://rusefi.com/docs/pinouts/proteus/

[rusefillc]

[rusefillc]

Switching from FTP to SFTP has resolved this issue