G
Gene
Our host is web.com (formerly Interland.com). Today I could not log onto our
site to update two pages, receiving the FP error message:
Unable to open <website>.com Possible causes:
1. The web server may not have the FPSE installed.
2. The web server may be temporarily out of service.
3. If you are connecting through a proxy server, the proxy settings may be
incorrect.
4. An error may have occurred in the web server.
When I log on to our Control Panel and try to do a Fix/Check of the FPSE it
fails with a similar message. Our Email contact form is not working, so the
FPSE are broken (they worked yesterday). We do not connect through a proxy
server.
After this happened over several hours I called Web.com. Their tech support
(in Columbia, South America) told me FP has a size limit of 1000 pages and I
have 1054 pages.
I know from reading a posting by Ron Symonds ("Ronx") that FP has no page
limit (thanks, Ron!), so I am about to call them back and go another round
with them.
Can anyone suggest any cause for this that is my fault? Something I can do?
Or is the only thing I can do is convince Web.com to reboot the server,
etc.?
Thanks,
Gene
site to update two pages, receiving the FP error message:
Unable to open <website>.com Possible causes:
1. The web server may not have the FPSE installed.
2. The web server may be temporarily out of service.
3. If you are connecting through a proxy server, the proxy settings may be
incorrect.
4. An error may have occurred in the web server.
When I log on to our Control Panel and try to do a Fix/Check of the FPSE it
fails with a similar message. Our Email contact form is not working, so the
FPSE are broken (they worked yesterday). We do not connect through a proxy
server.
After this happened over several hours I called Web.com. Their tech support
(in Columbia, South America) told me FP has a size limit of 1000 pages and I
have 1054 pages.
I know from reading a posting by Ron Symonds ("Ronx") that FP has no page
limit (thanks, Ron!), so I am about to call them back and go another round
with them.
Can anyone suggest any cause for this that is my fault? Something I can do?
Or is the only thing I can do is convince Web.com to reboot the server,
etc.?
Thanks,
Gene