Publishing is w/ Namecheap
Forum rules
IMPORTANT NOTE!!
DO YOU HAVE A QUESTION OR PROBLEM AND WANT QUICK HELP?
THEN PLEASE SHARE A "DEMO" PROJECT.
PLEASE READ THE FORUM RULES BEFORE YOU POST:
http://www.wysiwygwebbuilder.com/forum/viewtopic.php?f=12&t=1901
MUST READ:
http://www.wysiwygwebbuilder.com/getting_started.html
WYSIWYG Web Builder FAQ
IMPORTANT NOTE!!
DO YOU HAVE A QUESTION OR PROBLEM AND WANT QUICK HELP?
THEN PLEASE SHARE A "DEMO" PROJECT.
PLEASE READ THE FORUM RULES BEFORE YOU POST:
http://www.wysiwygwebbuilder.com/forum/viewtopic.php?f=12&t=1901
MUST READ:
http://www.wysiwygwebbuilder.com/getting_started.html
WYSIWYG Web Builder FAQ
Publishing is w/ Namecheap
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
Re: Publishing is w/ Namecheap
Why are you using port 52515?
And why aren't you using passive mode?
And why aren't you using passive mode?
Re: Publishing is w/ Namecheap
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.
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.
Re: Publishing is w/ Namecheap
Just because you use pert 21 doesn't mean the server uses it.
Alan
Alan
Re: Publishing is w/ Namecheap
I suggest to enable passive mode, because PORT mode will not get through your firewall.
Re: Publishing is w/ Namecheap
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.
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.
Re: Publishing is w/ Namecheap
I am experiencing these exact issues with my namecheap hosting several wysiwyg projects. just is in last month.
Re: Publishing is w/ Namecheap
Did you set passive mode?
Or maybe they have switched to Secure FTP?
Or maybe they have switched to Secure FTP?
Re: Publishing is w/ Namecheap
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?
Re: Publishing is w/ Namecheap
Maybe your website space is full?
What is the exact error?
What is the exact error?
Re: Publishing is w/ Namecheap
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 ***
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 ***
Re: Publishing is w/ Namecheap
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
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
Re: Publishing is w/ Namecheap
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.
This means that if you have a firewall or router that the connection will fail.
Re: Publishing is w/ Namecheap
If this continues, try publishing to your local drive and use Filezilla or similar ftp program to upload and see what you get.
Re: Publishing is w/ Namecheap
@bkjohns
That's what I do - if i try to publish full website from within WYSIWYG the program very often locks up and has done for some time.
I found if i publish locally and use Filezilla I don't have any problems and I also have a complete copy on my hard drive as a backup so not all bad.
I should add that I assumed it was some settings on my laptop as no-one else seemed to have had the issue.
That's what I do - if i try to publish full website from within WYSIWYG the program very often locks up and has done for some time.
I found if i publish locally and use Filezilla I don't have any problems and I also have a complete copy on my hard drive as a backup so not all bad.
I should add that I assumed it was some settings on my laptop as no-one else seemed to have had the issue.
Re: Publishing is w/ Namecheap
Ok. we got this resolved with namecheap. The issue is they need me to change to SFTP. I was publishing via FTP. But in switching to SFTP they were not giving me the correct information to change the port number to.
Once I changed the port number to the correct namecheap port everything starting publishing fine.
Thanks
Once I changed the port number to the correct namecheap port everything starting publishing fine.
Thanks
Re: Publishing is w/ Namecheap
Passive Mode has always been checked marked. Never been changed. Same Virgin Mobile router for over a year. I have never installed a firewall.
I have not changed any settings since the initial setup. Has always worked fine and never got a Fail until recently.
Re: Publishing is w/ Namecheap
I'm sorry, but the log indicates that passive mode is not enabled.
200 PORT command successful
425 Could not open data connection to port
Re: Publishing is w/ Namecheap
So in order to set WYSIWYG to use passive mode,
I would have to un-check the 'Use Passive Mode for Transfers" box ?
I would have to un-check the 'Use Passive Mode for Transfers" box ?
Re: Publishing is w/ Namecheap
No, the option should be checked.