Publishing is w/ Namecheap
Posted: 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
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