www.wysiwygwebbuilder.com

Today, I discovered "Publishing" changes to a webpage results in Failure.
Both in publishing only "Changes" and "Complete Page".
This error has never previously occurred.
The updated webpage "Previews" correctly with the changes; however Publishing fails.
I note new v21 update occurred March 8 - any correlation to the publishing failure?
Any help will be appreciated...thanks!
JimRicketts/tmhaudio.com

There are no known issues with publishing in WB21. It works the same as in previous versions.
But maybe your firewall blocks the connection with the server?

If you need further assistance then please set the log level to all and share the log.

Related FAQ:
https://www.wysiwygwebbuilder.com/commu ... hp?t=36493

Thank you Pablo for your reply.

Additional notes:
I'm still using Version 17.
When adding a simple "TEST" in a text window on my "Test WebPage", the "Preview" updates perfectly.
However, when I then publish, a "PUBLISH FAILED" is noted in update window. Here is publishing log:

*** START OF PUBLISH ***
Scanning publish folder...
Found 33 file(s).
Transfering 33 file(s) using SFTP with SSH2 (Secure Shell)
Connecting to chi209.greengeeks.net (Attempt 1 of 3)
WWB-FTP-Log:
AuthenticatePw:
DllDate: Mar 23 2022
WWB-FTP-Version: 9.5.0.90
UnlockPrefix: PBLSFS.CB1052023
Architecture: Little Endian; 64-bit
Language: Visual C++ / x64
VerboseLogging: 0
authenticatePw:
hostname: chi209.greengeeks.net
port: 22
serverVersion: SSH-2.0-OpenSSH_8.0
Component successfully unlocked using purchased unlock code.
idleTimeoutMs: 30000
sshAuthenticatePw:
requestUserAuthService:
sendServiceRequest:
svcName: ssh-userauth
SentServiceReq: ssh-userauth
--sendServiceRequest
ssh-userauth service accepted.
--requestUserAuthService
AuthMethods: publickey,gssapi-keyex,gssapi-with-mic
No valid authentication methods found.
--sshAuthenticatePw
--authenticatePw
Failed.
--AuthenticatePw
--WWB-FTP-Log

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

The error seems to indicate that something is wrong with the password.
Maybe the web host has changed the password or another configuration setting??

Note that if you are still using WB17 and you did not change anything yourself then this is most like and issue on the server side.

Server Host replied:
"Based on that log it looks like you are using SFTP, which would explain the issue.
We recently made a security change to SSH(SFTP) which now requires a key to be used.
So there would be 2 options, if the software supports it, switching from SFTP to plain FTP would be the easiest option."

Action: I changed to "Standard FTP" and it published without errors.
QUESTION: Is there a down side to using "Standard FTP" vs SSH(SFTP) + key?

Thank you, Pablo for your help!
Jim Ricketts/tmhaudio

Standard FTP is less secure.

Which host do you have? I have not heard about a key requirement before.

GreenGeeks.com