[infrancer]

Publii does not synchronize via ftp/sftp after update

I have two identical Publii on two laptops.
First update to Version: 0.43.1 (build 16393)
During the upload sites, process just froze on the “uploading”
https://i.imgur.com/cGLvmcQ.jpg

Test connection – just froze without errors
https://i.imgur.com/8Sey2Pr.jpg

Second laptop, everything works correctly (Publii not updated)
https://i.imgur.com/tbvKPJJ.jpg

P.S

I used to see this problem when I was updating Publii or migrating sites to another folder.
I fixed this just by removing site and back it from the backup.
Everything started working. Now this method does not help.

 

P.S.S

Deployment log

[Fri, 27 Oct 2023 13:23:56 GMT] [connection] < '220 2001:67c:2070:c817::1 FTP server ready\r\n'
[Fri, 27 Oct 2023 13:23:56 GMT] [parser] < '220 2001:67c:2070:c817::1 FTP server ready\r\n'
[Fri, 27 Oct 2023 13:23:56 GMT] [parser] Response: code=220, buffer='2001:67c:2070:c817::1 FTP server ready'
[Fri, 27 Oct 2023 13:23:56 GMT] [connection] > 'USER dolya2_ftp'
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] < '331 Password required for dolya2_ftp\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [parser] < '331 Password required for dolya2_ftp\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [parser] Response: code=331, buffer='Password required for dolya2_ftp'
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] > PASS ******************************
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] < "230-User 'dolya2_ftp' allowed by access rules\r\n" +
  '230 User dolya2_ftp logged in\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [parser] < "230-User 'dolya2_ftp' allowed by access rules\r\n" +
  '230 User dolya2_ftp logged in\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [parser] Response: code=230, buffer="User 'dolya2_ftp' allowed by access rules\r\nUser dolya2_ftp logged in"
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] > 'FEAT'
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] < '211-Features:\r\n AUTH TLS\r\n CCC\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] < ' CLNT\r\n EPRT\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] < ' EPSV\r\n' +
  ' HOST\r\n' +
  ' MDTM\r\n' +
  ' MFF modify;UNIX.group;UNIX.mode;\r\n' +
  ' MFMT\r\n' +
  ' MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.groupname*;UNIX.mode*;UNIX.owner*;UNIX.ownername*;\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] < ' PBSZ\r\n PROT\r\n RANG STREAM\r\n REST STREAM\r\n SIZE\r\n SSCN\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] < ' TVFS\r\n211 End\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [parser] < '211-Features:\r\n' +
  ' AUTH TLS\r\n' +
  ' CCC\r\n' +
  ' CLNT\r\n' +
  ' EPRT\r\n' +
  ' EPSV\r\n' +
  ' HOST\r\n' +
  ' MDTM\r\n' +
  ' MFF modify;UNIX.group;UNIX.mode;\r\n' +
  ' MFMT\r\n' +
  ' MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.groupname*;UNIX.mode*;UNIX.owner*;UNIX.ownername*;\r\n' +
  ' PBSZ\r\n' +
  ' PROT\r\n' +
  ' RANG STREAM\r\n' +
  ' REST STREAM\r\n' +
  ' SIZE\r\n' +
  ' SSCN\r\n' +
  ' TVFS\r\n' +
  '211 End\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [parser] Response: code=211, buffer='Features:\r\n' +
  ' AUTH TLS\r\n' +
  ' CCC\r\n' +
  ' CLNT\r\n' +
  ' EPRT\r\n' +
  ' EPSV\r\n' +
  ' HOST\r\n' +
  ' MDTM\r\n' +
  ' MFF modify;UNIX.group;UNIX.mode;\r\n' +
  ' MFMT\r\n' +
  ' MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.groupname*;UNIX.mode*;UNIX.owner*;UNIX.ownername*;\r\n' +
  ' PBSZ\r\n' +
  ' PROT\r\n' +
  ' RANG STREAM\r\n' +
  ' REST STREAM\r\n' +
  ' SIZE\r\n' +
  ' SSCN\r\n' +
  ' TVFS\r\n' +
  'End'
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] > 'TYPE I'
[Fri, 27 Oct 2023 13:23:57 GMT] [connection] < '200 Type set to I\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [parser] < '200 Type set to I\r\n'
[Fri, 27 Oct 2023 13:23:57 GMT] [parser] Response: code=200, buffer='Type set to I'
[Fri, 27 Oct 2023 13:24:02 GMT] [connection] > 'PASV'

 

[Hame]

I’m experiencing something similar.

I can fix it by following another poster’s suggestion to replace the “files.publii.json” file on the server with my local one… which fixes it once. The next time I try to publish a new post, the site tries to re-upload all the files and hangs partway through.

[infrancer]

Hame wrote:

I’m experiencing something similar.

I can fix it by following another poster’s suggestion to replace the “files.publii.json” file on the server with my local one… which fixes it once. The next time I try to publish a new post, the site tries to re-upload all the files and hangs partway through.

Replace “files.publii.json” doesn’t work.
In ftp logs i see that the program connected via login/password and …
Nothing else happens.
If you press “cancel” you get an error

[kensquires]

Simple/easy fix is to use Filezilla or your favorite FTP program.

I get that using a secondary program to do the job that Publii should do kind of sounds dumb but Filezilla / dedicated FTP program will have certain advantages like faster uploads cause it’ll upload multiple files at once as Publii only does one at a time.

It’s also just an easy fix until the dev team fixes it.

[infrancer]

kensquires wrote:

Simple/easy fix is to use Filezilla or your favorite FTP program.

I get that using a secondary program to do the job that Publii should do kind of sounds dumb but Filezilla / dedicated FTP program will have certain advantages like faster uploads cause it’ll upload multiple files at once as Publii only does one at a time.

It’s also just an easy fix until the dev team fixes it.

Ohh
I use export to zip and upload to server via winscp (a client), but it is not faster or more convenient.

[kensquires]

Uploading may/may not be faster with Winscp or any client it depends on the settings as by default many may just upload one file at a time, similar to publii. Using a 3rd party client would not make things more convenient just because it would add the additional step

Regardless I got looking at the few pictures you provided including the javascript error

I have had the javascript error myself, for me I just close Publii and reopen it and things seem to work after that.

as for Publii freezing during uploading that can be two different things

1 – the file it’s uploading can be big and it’s just taking a longer time

2 – the server is down because, by the looks of it, you have no errors in the log you posted.

also by the looks of it your website is now down, unless you removed it yourself.

If you don’t mind me asking, who is hosting your website?

 

[infrancer]

Site works (I have several sites at publii on different servers) and the server works. on the «home» computer with «old » version updates passes correctly.

[kensquires]

I guess either stay with the older version until it gets fixed or try the alpha ver 44 they got posted.

Nothing about the FTP got changed in the alpha but it may just be dumb luck that it works better than the hotfix

[Tomasz Dziuda]

Hi,

Do you have these issues in v.0.43.1 only? In v.0.43 it was ok?

--
Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!

[Author]

Posts