Are you having FTP issues? We want to help!

RapidWeaver Classic General
1

If you’re having issues publishing your site with RapidWeaver 6.2.3 or newer can you please do the following:

  1. Switch the “Enable upload logging” option on in the RapidWeaver Preferences.

    Screen Shot 2015-07-12 at 20.11.22.png1124×900 225 KB

  2. Then try to upload your website, if it fails go to the “Help” menu and and select “Copy Support Logs”.

    Screen Shot 2015-07-12 at 20.14.19.png1634×558 894 KB

  3. The support logs will then be in your clipboard, paste them into a plain text file and email it to support@realmacsoftware.com

We really want to make sure FTP is rock solid for all RapidWeaver users and we can only do this with your help!

Thanks,
Dan

2

I think this is a FTP bug… whenever I do an update which needs to publish over 100-200 files it seems to lose count. Then at the end after uploading almost all files it gives a message that publishing fails for instance 371 of 372 files uploaded…

BTW I did a screen capture of this and tried to upload it for you but I apparently am a new user on these forums (new software) so it wouldn’t let me … :frowning:

Then the next time I publish it doesn’t seem to have anything to publish… so it must have lost count?

Best regards

Paul Shard
(longtime RW user :smiley:

1 Like
3

Could you post/host it somewhere else? For example, your FTP server, Droplr, or CloudApp?

4

I’ve noticed that I cannot upload my site if I am on the ‘home’ page in preview mode.

If I click on another page and change to edit mode, it uploads straight away.

5

this is very “funny”. I kept (and still keep) posting error reports for years regarding ftp upload problems with rw5 and NEVER heard back from you. rw5 still crashes/stalls quite often during the upload process. I am very upset about this!

6

I sent a support log in a week ago with no reply or acknowledgement. It would appear that getting back to those who send in these reports is not a part of their process.

7

I was using FTPS to connect to server and from the log I found RW6 uses PROT C to disable both integrity and privacy after authentication. But the FTP server does not support this. Please RM remove this default action and use the PROT P if PROT C is rejected by server?

19/7/15 4:20:42.883 pm RapidWeaver 6[4395] Rebuilt URL to: ftp://XXX.XXX.XXX.XXX/
19/7/15 4:20:42.886 pm RapidWeaver 6[4395] Connection 2 seems to be dead!
19/7/15 4:20:42.886 pm RapidWeaver 6[4395] Closing connection 2
19/7/15 4:20:43.298 pm RapidWeaver 6[4395] Trying xxx.xxx.xxx.xxx…
19/7/15 4:20:43.304 pm RapidWeaver 6[4395] Connected to XXX.XXX.XXX.XXX (xxx.xxx.xxx.xxx) port 21 (#3)
19/7/15 4:20:43.311 pm RapidWeaver 6[4395] 220-Microsoft FTP Service
19/7/15 4:20:43.311 pm RapidWeaver 6[4395] 220 Welcome to XXXXXXXXX
19/7/15 4:20:43.311 pm RapidWeaver 6[4395] AUTH SSL
19/7/15 4:20:43.317 pm RapidWeaver 6[4395] 234 AUTH command ok. Expecting TLS Negotiation.
19/7/15 4:20:43.317 pm RapidWeaver 6[4395] SSL re-using session ID
19/7/15 4:20:43.406 pm RapidWeaver 6[4395] TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
19/7/15 4:20:43.406 pm RapidWeaver 6[4395] Server certificate: sweb.cityu.edu.hk
19/7/15 4:20:43.407 pm RapidWeaver 6[4395] Server certificate: COMODO RSA Organization Validation Secure Server CA
19/7/15 4:20:43.407 pm RapidWeaver 6[4395] Server certificate: COMODO RSA Certification Authority
19/7/15 4:20:43.407 pm RapidWeaver 6[4395] Server certificate: AddTrust External CA Root
19/7/15 4:20:43.408 pm RapidWeaver 6[4395] USER kincau
19/7/15 4:20:43.412 pm RapidWeaver 6[4395] 331 Password required
19/7/15 4:20:43.413 pm RapidWeaver 6[4395] PASS [REDACTED]
19/7/15 4:20:43.451 pm RapidWeaver 6[4395] 230 User logged in.
19/7/15 4:20:43.451 pm RapidWeaver 6[4395] PBSZ 0
19/7/15 4:20:43.456 pm RapidWeaver 6[4395] 200 PBSZ command successful.
19/7/15 4:20:43.456 pm RapidWeaver 6[4395] PROT C
19/7/15 4:20:43.461 pm RapidWeaver 6[4395] 534 Policy requires SSL.
19/7/15 4:20:43.461 pm RapidWeaver 6[4395] PWD
19/7/15 4:20:43.466 pm RapidWeaver 6[4395] 257 “/xxxxxx” is current directory.
19/7/15 4:20:43.467 pm RapidWeaver 6[4395] Entry path is ‘/xxxxxx’
19/7/15 4:20:43.467 pm RapidWeaver 6[4395] PASV
19/7/15 4:20:43.467 pm RapidWeaver 6[4395] Connect data stream passively
19/7/15 4:20:43.468 pm RapidWeaver 6[4395] ftp_perform ends with SECONDARY: 0
19/7/15 4:20:43.473 pm RapidWeaver 6[4395] 227 Entering Passive Mode (xxx,xxx,xxx,xxx,xxx,xxx).
19/7/15 4:20:43.473 pm RapidWeaver 6[4395] Trying xxx.xxx.xxx.xxx…
19/7/15 4:20:43.473 pm RapidWeaver 6[4395] Connecting to xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) port 55263
19/7/15 4:20:43.478 pm RapidWeaver 6[4395] Connected to XXX.XXX.XXX.XXX (xxx.xxx.xxx.xxx) port 21 (#3)
19/7/15 4:20:43.479 pm RapidWeaver 6[4395] TYPE A
19/7/15 4:20:43.483 pm RapidWeaver 6[4395] 200 Type set to A.
19/7/15 4:20:43.483 pm RapidWeaver 6[4395] LIST
19/7/15 4:20:43.488 pm RapidWeaver 6[4395] 534 Protection level negotiation failed.
19/7/15 4:20:43.488 pm RapidWeaver 6[4395] RETR response: 534
19/7/15 4:20:43.488 pm RapidWeaver 6[4395] Remembering we are in dir “”
19/7/15 4:20:43.489 pm RapidWeaver 6[4395] Connection #3 to host XXX.XXX.XXX.XXX left intact
19/7/15 4:20:43.489 pm RapidWeaver 6[4395] CURL ERROR: 19 - Couldn’t sign in to your FTPS server

8

@colorwave - it’s probably because we’re still looking into it. You can always email us again to chase it up.

Please remember, there’s only 4 of us in the office and we’re doing the best we can!

Thanks,
Dan

9

@dan I meant that many or most support emails that I have sent in to developers large or small are acknowledged, even if it is by an automated system. I understand that there isn’t much to say until the problems are sorted out, but it is nice to know that the log was received when it is manually retrieved from a log and sent in (not just an automated crash report). I certainly don’t expect a hand written note every time RW crashes and you are notified.

It is worth noting that I am beta testing an updated plugin that no longer supports RW5 code, and my RW publishing has been rock solid since. I am hopeful that better days are ahead for most of us, when it comes to in app publishing.

10

@skaicaptain - I’d advise you upgrade to RW 6 - the FTP engine is much better and improving with every release.

11

@colorwave I’ve just taken a look - it appears a miscommunication meant that this email wasn’t picked up while I was away. You’ll hear from me shortly.

12

We’ll see what we can do! Thanks for the report.

13

Thanks for reply, now i need to export the website and use 3rd party ftp client for uploading. Both CyberDuck and FileZilla can connect and upload files to this ftps server, so I am very sure this is the bug in RM6. This is inconvenient and hope can be solved in the next update.

14

We’re looking into it, but I cannot guarantee it will make 6.2.4, as we’re aiming to keep shipping updates on a regular basis.

15

@dan thanks for suggesting! but we had this discussion in detail before why this is no option for me. rw6 has many shortcomings in my case and that does not seem to change ever. so I will have to stick and suffer with rw5 as long as possible.

16

@skaicaptain I’m not sure what RW6 shortcomings you’re referring too, can you please list them out here?

17

@dan please understand if I don’t. I did so extensively when rw6 was in beta and also later. it is clear by now (nik made it clear) that certain gui problems and features missing won’t come back again. also ftp does seem to be still very problematic. so no. sorry. no switch for me. best wishes, kai

18

@skaicaptain RW6 has had a lot of updates since it was in beta. Please could you list the shortcomings so we can fix them in future builds?

19

@dan I don’t want to go into it again and again. for me the discussion is in the past and nik made it clear, too. but thanks for asking and all the best. kai (I switched already because of rw6 to another environment and am quite happy now. I just have so many projects still based on rw5 so I have to stick with it for a while)

20

Thanks Dan. I have since upgraded again and it looks like you FIXED the problem in one of the point releases! Normally it would miss one or two files from the publishing and report an error. Now it seems to be OK. I’ll report again if it recurs.