Page 1 of 1

Error publishing in WB 15.1

Posted: Tue Oct 15, 2019 8:31 am
by longman
Hi pablo,

i just got WB 15.1, I get this error when publishing my site:
Details:
The server returned extended information
200 TYPE is now 8-bit binary
425 Unable to identify the local data socket: Address already in use
200 TYPE is now 8-bit binary
500 I won't open a connection to 10.8.0.9 (only to 45.9.249.76)
500 Unknown command

Closing FTP connection...
Removing temporary files...
Publish failed!
*** END OF PUBLISH ***
How to solve this?

Ty

Re: Error publishing in WB 15.1

Posted: Tue Oct 15, 2019 9:03 am
by Pablo
Did it previously work?
If yes, then maybe there is a problem on the host side?
Or maybe your firewall blocks the connection?

Related FAQ:
http://www.wysiwygwebbuilder.com/forum/ ... 10&t=36493

Re: Error publishing in WB 15.1

Posted: Tue Oct 15, 2019 10:43 am
by longman
It worked in version 14.

My error number is 12003, its not in FAQ section.

Re: Error publishing in WB 15.1

Posted: Tue Oct 15, 2019 10:48 am
by longman
my firewall is off.

It keeps uploading and around 50% it suddenly fails...

Re: Error publishing in WB 15.1

Posted: Tue Oct 15, 2019 11:24 am
by Pablo
Did you use the same settings in WB14?
Does it work when you switch to 'winsock'?

Note that the error normally indicates a firewall or router related issue:
I won't open a connection to 10.8.0.9 (only to 45.9.249.76)

Re: Error publishing in WB 15.1

Posted: Tue Oct 15, 2019 12:37 pm
by longman
I been all day trying to publish, it fails every time :(

I tried to Reset the network in my windows, it did not help.

Firewall is and always been off in my windows.

As for router, I do not know what to do, should I bring a network specialist or someone?

Re: Error publishing in WB 15.1

Posted: Tue Oct 15, 2019 1:47 pm
by longman
I can Test and Explore the FTP in publish window, all are ok.

But when it comes to publishing, it publishes like 30-40% and suddenly fails.

It happens every single time, so weird

Re: Error publishing in WB 15.1

Posted: Tue Oct 15, 2019 2:34 pm
by Pablo
Did you try with 'winsock' selected?
What is the error in that case?