www.wysiwygwebbuilder.com

Hi All

Just updated to v20.0.4 and can no longer publish. I get the following error:

*** START OF PUBLISH ***
Scanning publish folder...
Found 3 file(s).
Transfering 3 file(s) using FTP (standard File Transfer Protocol)
Connecting to ftp.mywebsite.club (Attempt 1 of 3)
Log:
Connect_Ftp2:
DllDate: Feb 27 2024
Version: 9.5.0.97
UnlockPrefix: PABLOS
UnlockStatus: 2
Architecture: Little Endian; 64-bit
Language: Visual C++ / x64
VerboseLogging: 0
ProgressMonitoring:
enabled: no
heartbeatMs: 0
sendBufferSize: 65536
--ProgressMonitoring
ImplicitSsl: 0
AuthTls: 0
AuthSsl: 0
ftpConnect:
Hostname: ftp.mywebsite.club
Port: 21
IdleTimeoutMs: 60000
socket2Connect:
connect2:
connectSocket_v2:
connect_domain:
ckDnsResolveDomainIPv4_n:
domainName: ftp.mywebsite.club
--ckDnsResolveDomainIPv4_n
ipv4_address: 45.8.227.140
--connect_domain
--connectSocket_v2
--connect2
--socket2Connect
socketOptions:
SO_SNDBUF: 262144
SO_RCVBUF: 4194304
TCP_NODELAY: 1
SO_KEEPALIVE: 1
--socketOptions
readCommandResponse:
replyLineQP: 220 FTP server ready
--readCommandResponse
initialStatus: 220
initialResponse: 220 FTP server ready
--ftpConnect
tlsSessionInfo:
forceReuseTlsSession: False
tlsVersionMajor: 0
tlsVersionMinor: 0
sessionId: (empty)
masterSecretLen: 0
tls13_resumption_secret_len: 0
prfHashAlg: None
We do NOT have the TLS server certs.
We do NOT have a TLS 1.3 session ticket.
--tlsSessionInfo
Logging in...
Login:
sendCommand:
sendingCommand: USER mywebsite.club
--sendCommand
readCommandResponse:
replyLineQP: 331 Password required for mywebsite.club
--readCommandResponse
sendCommand:
sendingCommand: PASS *
--sendCommand
readCommandResponse:
replyLineQP: 530 Login failed: please verify the username and password supplied, and tha=
t FTP locking is either disabled or permitted for your current IP address
--readCommandResponse
--Login
Failed.
--Connect_Ftp2
--Log

Failed to connect to ftp.mywebsite.club (Attempt 1 of 3)
Connecting to ftp.mywebsite.club (Attempt 2 of 3)
Log:
Connect_Ftp2:
DllDate: Feb 27 2024
Version: 9.5.0.97
UnlockPrefix: PABLOS
UnlockStatus: 2
Architecture: Little Endian; 64-bit
Language: Visual C++ / x64
VerboseLogging: 0
ProgressMonitoring:
enabled: no
heartbeatMs: 0
sendBufferSize: 65536
--ProgressMonitoring
ImplicitSsl: 0
AuthTls: 0
AuthSsl: 0
ftpConnect:
Hostname: ftp.mywebsite.club
Port: 21
IdleTimeoutMs: 60000
socket2Connect:
connect2:
connectSocket_v2:
connect_domain:
ckDnsResolveDomainIPv4_n:
domainName: ftp.mywebsite.club
--ckDnsResolveDomainIPv4_n
ipv4_address: 45.8.227.140
--connect_domain
--connectSocket_v2
--connect2
--socket2Connect
socketOptions:
SO_SNDBUF: 262144
SO_RCVBUF: 4194304
TCP_NODELAY: 1
SO_KEEPALIVE: 1
--socketOptions
readCommandResponse:
replyLineQP: 220 FTP server ready
--readCommandResponse
initialStatus: 220
initialResponse: 220 FTP server ready
--ftpConnect
tlsSessionInfo:
forceReuseTlsSession: False
tlsVersionMajor: 0
tlsVersionMinor: 0
sessionId: (empty)
masterSecretLen: 0
tls13_resumption_secret_len: 0
prfHashAlg: None
We do NOT have the TLS server certs.
We do NOT have a TLS 1.3 session ticket.
--tlsSessionInfo
Logging in...
Login:
sendCommand:
sendingCommand: USER mywebsite.club
--sendCommand
readCommandResponse:
replyLineQP: 331 Password required for mywebsite.club
--readCommandResponse
sendCommand:
sendingCommand: PASS *
--sendCommand
readCommandResponse:
replyLineQP: 530 Login failed: please verify the username and password supplied, and tha=
t FTP locking is either disabled or permitted for your current IP address
--readCommandResponse
--Login
Failed.
--Connect_Ftp2
--Log

Failed to connect to ftp.mywebsite.club (Attempt 2 of 3)
Connecting to ftp.mywebsite.club (Attempt 3 of 3)
Log:
Connect_Ftp2:
DllDate: Feb 27 2024
Version: 9.5.0.97
UnlockPrefix: PABLOS
UnlockStatus: 2
Architecture: Little Endian; 64-bit
Language: Visual C++ / x64
VerboseLogging: 0
ProgressMonitoring:
enabled: no
heartbeatMs: 0
sendBufferSize: 65536
--ProgressMonitoring
ImplicitSsl: 0
AuthTls: 0
AuthSsl: 0
ftpConnect:
Hostname: ftp.mywebsite.club
Port: 21
IdleTimeoutMs: 60000
socket2Connect:
connect2:
connectSocket_v2:
connect_domain:
ckDnsResolveDomainIPv4_n:
domainName: ftp.mywebsite.club
--ckDnsResolveDomainIPv4_n
ipv4_address: 45.8.227.140
--connect_domain
--connectSocket_v2
--connect2
--socket2Connect
socketOptions:
SO_SNDBUF: 262144
SO_RCVBUF: 4194304
TCP_NODELAY: 1
SO_KEEPALIVE: 1
--socketOptions
readCommandResponse:
replyLineQP: 220 FTP server ready
--readCommandResponse
initialStatus: 220
initialResponse: 220 FTP server ready
--ftpConnect
tlsSessionInfo:
forceReuseTlsSession: False
tlsVersionMajor: 0
tlsVersionMinor: 0
sessionId: (empty)
masterSecretLen: 0
tls13_resumption_secret_len: 0
prfHashAlg: None
We do NOT have the TLS server certs.
We do NOT have a TLS 1.3 session ticket.
--tlsSessionInfo
Logging in...
Login:
sendCommand:
sendingCommand: USER mywebsite.club
--sendCommand
readCommandResponse:
replyLineQP: 331 Password required for mywebsite.club
--readCommandResponse
sendCommand:
sendingCommand: PASS *
--sendCommand
readCommandResponse:
replyLineQP: 530 Login failed: please verify the username and password supplied, and tha=
t FTP locking is either disabled or permitted for your current IP address
--readCommandResponse
--Login
Failed.
--Connect_Ftp2
--Log

Removing temporary files...
Publish failed!
*** END OF PUBLISH ***

i have swapped the readl domain name for something else.

Nothing has changed since the last upload, hosting, passwords, etc.

Anyone got any ideas?

TIA
Paul

EDIT: Just tried ma couple of other sites - can't publish those either ;( Same error message.
p.s. What is the 'UnlockPrefix: PABLOS' for? Don't recal seeing that?

This has nothing to do with the update. Nothing has changed related to publishing.

The error indicates that either your username or password is correct.

Note: the software does not verify these values, they will be sent to the server as you have entered it.
So, this is a response from the server based on your input.

For all my web sites?

Can io revert the update and go back to 20.3.xx

Thanks

Tried 1/2 dozen sites now - all get the same error message!

I'll contact the hosting provider to see if that have any clue.

Cheers
Paul

I might know what it is.... just doing some testing....

OK, for whatever reason, my Hosting had put a Lock on my IP address!

So, if you get something like this, just check (as I did) with a simple FTP app and see if that works for you.

Pablo, thanks for you help once again!

Cheers
Paul