Publishing is w/ Namecheap

All WYSIWYG Web Builder support issues that are not covered in the forums below.
Forum rules
PLEASE READ THE FORUM RULES BEFORE YOU POST:
viewtopic.php?f=12&t=1901

MUST READ:
http://www.wysiwygwebbuilder.com/getting_started.html
WYSIWYG Web Builder FAQ
pacstar
 
 
Posts: 225
Joined: Wed Nov 14, 2018 8:49 pm
Contact:

Publishing is w/ Namecheap

Post by pacstar » Tue Feb 18, 2020 6:42 pm

Hi Pablo,

I've been working on a publishing failure issue with Namecheap. Below is their responses to the correspondence I have had with them:

Here is the error I'm getting:

Internet Exception Error 12003

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
200 PORT command successful
425 Could not open data connection to port 52515: Connection refused

Closing FTP connection...
Removing temporary files...
Publish failed!

**************************************************************


According to our check, there are some mod_security rules which result in blocks for your site. We have whitelisted the rule that was triggered.

Mod_Security is an Apache module that helps to protect your website from various attacks. Mod_Security is used to block commonly known exploits by the use of regular expressions and rule sets. We installed a Mod_Security for increasing the security of our servers. It is an Apache module that works as a web application firewall. It blocks known exploits and provides protection from a range of attacks against web applications. Its activity may cause such issues from time to time when requests sent to the server match with mod_sec rules. Sometimes such requests are false-positive.

Please check it on your side and let us know if the issue still persists. If so, please provide us with a step-by-step guide on how to reproduce it on our end.

**************************************************
----> Issues still persist, I discovered switching to winsock from wininet as the FTP engine resolved the issue
**************************************************

Per our check, there are no new logs on the server. We can try disabling ModSecurity for your hosting account for test purposes.

However, we don't recommend this as it was implemented for security reasons and your account becomes vulnerable to hacker attempts when Mod_Security disabled.

You may just use the 'winsock' option since it's working correctly.


***********************************************
-----> just switching to winsock doesn't seem to be a real resolution to me since it has been working fine for over a year now as wininet, and it appears wininet is a better option.
***********************************************
Unfortunately, as a hosting provider, we specialize in certain areas only and may not know all the specifications of some software/applications.

We'd recommend contacting a WYSIWYG Web Builder support to investigate the issue deeper. If they are able to specify what is the reason of the issue, we will be happy to investigate it deeper.


************************************************

We'd recommend performing the following steps:
1. change the FTP connection to the passive mode (so that WYSIWYG Web Builder will use the default server's FTP port for the connection);
2. set the limit for the simultaneous connections to 3 (to prevent your external IP address to be blocked by the server's firewalls).

In case you cannot find these settings in WYSIWYG Web Builder, please contact their support to check where this should be configured.


***********************************************

I'm currently still using winsock to publish, but I thought you might want the information they sent me.

Thanks

User avatar
Pablo
 
Posts: 23401
Joined: Tue Mar 28, 2006 12:00 pm
Location: Europe
Contact:

Re: Publishing is w/ Namecheap

Post by Pablo » Tue Feb 18, 2020 7:02 pm

Why are you using port 52515?
And why aren't you using passive mode?

pacstar
 
 
Posts: 225
Joined: Wed Nov 14, 2018 8:49 pm
Contact:

Re: Publishing is w/ Namecheap

Post by pacstar » Tue Feb 18, 2020 9:17 pm

Pablo,

See, that's whats funny. I am using passive mode, and I'm using port 21.

I have no idea what those numbers are referring to and why I am getting that response.

alan_sh
 
 
Posts: 796
Joined: Tue Jan 01, 2019 5:50 pm

Re: Publishing is w/ Namecheap

Post by alan_sh » Tue Feb 18, 2020 11:24 pm

Just because you use pert 21 doesn't mean the server uses it.

Alan

pacstar
 
 
Posts: 225
Joined: Wed Nov 14, 2018 8:49 pm
Contact:

Re: Publishing is w/ Namecheap

Post by pacstar » Tue Feb 18, 2020 11:34 pm

alan_sh wrote:
Tue Feb 18, 2020 11:24 pm
Just because you use pert 21 doesn't mean the server uses it.

Alan
Alan,

Yes, every time that number is different. It was just port 52515 that time.

User avatar
Pablo
 
Posts: 23401
Joined: Tue Mar 28, 2006 12:00 pm
Location: Europe
Contact:

Re: Publishing is w/ Namecheap

Post by Pablo » Wed Feb 19, 2020 7:07 am

I suggest to enable passive mode, because PORT mode will not get through your firewall.

pacstar
 
 
Posts: 225
Joined: Wed Nov 14, 2018 8:49 pm
Contact:

Re: Publishing is w/ Namecheap

Post by pacstar » Wed Feb 19, 2020 5:10 pm

Pablo,

As I said, Passive mode is enabled. It has always been enabled. Port #21 has always been selected. They have suggest different Ports to try, none of them worked.

WYSIWYG's test function comes back showing it is set up correctly using wininet, port 21 and passive mode. That is what my settings are and always have been.

I've had no issues publishing until the last month or 2. According to Namecheap, it appears to possibly be related to Mod_Security (I have no idea if it is or not).

If I try to publish just a couple of pages, it generally works, but if I try to publish more pages or my entire site, it fails every time.

Switching to winsock, has currently let me publish both large and small files. Still using passive mode and port 21.

I'm just passing the information on that was given to me. I'll be happy to pass any recommendations on to them, or get you in contact with them directly. Or if you think there is anything else I should try, let me know.

dnlyko
 
 
Posts: 95
Joined: Tue Mar 05, 2019 12:55 pm
Location: Canada

Re: Publishing is w/ Namecheap

Post by dnlyko » Wed May 20, 2020 11:15 am

I am experiencing these exact issues with my namecheap hosting several wysiwyg projects. just is in last month.

User avatar
Pablo
 
Posts: 23401
Joined: Tue Mar 28, 2006 12:00 pm
Location: Europe
Contact:

Re: Publishing is w/ Namecheap

Post by Pablo » Wed May 20, 2020 11:32 am

Did you set passive mode?
Or maybe they have switched to Secure FTP?

dnlyko
 
 
Posts: 95
Joined: Tue Mar 05, 2019 12:55 pm
Location: Canada

Re: Publishing is w/ Namecheap

Post by dnlyko » Wed May 20, 2020 11:55 am

Pablo wrote:
Wed May 20, 2020 11:32 am
Did you set passive mode?
Or maybe they have switched to Secure FTP?
Yes always using passive.
I don't think they changed to secure FTP.

Funny thing is...

When I publish 'Entire Web Site', it always fails.
If I publish 'Selected Page Only', it fails 50% of the time.

Yesterday I had to publish each page individually to get the site updated.
This morning I have been attempting for 2 hours to publish the entire site (maybe over 20 attempts) and on the second last attempt, WYSIWYG locked up. I had to use Task Manager to close WYSIWYG. I restarted WYSIWYG and made another attempt at 'Entire Web Site' and it was successful on 1st try. Strange?

User avatar
Pablo
 
Posts: 23401
Joined: Tue Mar 28, 2006 12:00 pm
Location: Europe
Contact:

Re: Publishing is w/ Namecheap

Post by Pablo » Wed May 20, 2020 12:02 pm

Maybe your website space is full?
What is the exact error?

dnlyko
 
 
Posts: 95
Joined: Tue Mar 05, 2019 12:55 pm
Location: Canada

Re: Publishing is w/ Namecheap

Post by dnlyko » Wed May 20, 2020 12:25 pm

Successfully uploaded file.
Uploading 'products/bathroom/fancybox/jquery.mousewheel-3.0.4.pack.js'...
Internet Exception Error 12003

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
200 PORT command successful
425 Could not open data connection to port
58828
58840
58857
61012


: Connection refused
Closing FTP connection...
Removing temporary files...
Publish failed!
*** END OF PUBLISH ***

dnlyko
 
 
Posts: 95
Joined: Tue Mar 05, 2019 12:55 pm
Location: Canada

Re: Publishing is w/ Namecheap

Post by dnlyko » Wed May 20, 2020 12:32 pm

Storage

139.64 MB of 20 GB in Use
Bandwidth2.00 GB of Unmetered Used

CPU

0% in Use

Memory

1.34 MB of 1024 MB Used
Virtual Memory0 MB of 0 MB Used
Hosted Domains2 of 3 Used

User avatar
Pablo
 
Posts: 23401
Joined: Tue Mar 28, 2006 12:00 pm
Location: Europe
Contact:

Re: Publishing is w/ Namecheap

Post by Pablo » Wed May 20, 2020 12:39 pm

The error indicates that you did not set passive mode.
This means that if you have a firewall or router that the connection will fail.

bkjohns
 
 
Posts: 170
Joined: Wed Nov 14, 2018 5:54 pm

Re: Publishing is w/ Namecheap

Post by bkjohns » Wed May 20, 2020 12:48 pm

If this continues, try publishing to your local drive and use Filezilla or similar ftp program to upload and see what you get.

Post Reply