Facebook
Twitter
C
chrisw914
Guest
Everytime i publish a frontpage site at the end i get a server error 413: entity too large. There is enough room for the file so i dont see why it is too large. Any ideas?
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
S
secretagentman
Guest
Yes, we have Windows 2003 Web Edition with IIS 6.0/FPSE 2002 and Plesk 6.5.1 and we are experiencing the same problem as well.
It appears in the patch documentation/text for 6.5.1 says this:
[-] Problem with large FrontPage Web publication eliminated.
Legend:
[+] new feature
[-] bug fixed or removed
[*] bug fixed and improvement made
So they think they've fixed the problem, but we are all experiencing the same issue.
It appears in the patch documentation/text for 6.5.1 says this:
[-] Problem with large FrontPage Web publication eliminated.
Legend:
[+] new feature
[-] bug fixed or removed
[*] bug fixed and improvement made
So they think they've fixed the problem, but we are all experiencing the same issue.
B
BrightAdmin
Guest
Hi,
The server may close the connection to prevent you from continuing the request. This may be a temporary error, please try again with some other files.
Regards,
Bright
The server may close the connection to prevent you from continuing the request. This may be a temporary error, please try again with some other files.
Regards,
Bright
S
secretagentman
Guest
I'm not sure it is a temporary problem seeing that the server always errors out at files >500K bytes. A customer has a MS-Access DB that will not upload. I've attempted to upload the same DB using the client Frontpage 2000, 2002 without success.
B
BrightAdmin
Guest
Hi,
May be the problem can only be resolved by examining by what your client system is trying to do, then discussing with your ISP why the Web server rejects the number of bytes sent by the client system.
Regards,
Bright
May be the problem can only be resolved by examining by what your client system is trying to do, then discussing with your ISP why the Web server rejects the number of bytes sent by the client system.
Regards,
Bright
S
secretagentman
Guest
Uhmm, I am the ISP.
And posting files >500K bytes is pretty common in hosting environments, especially if the file is a MS-Access DB.
And posting files >500K bytes is pretty common in hosting environments, especially if the file is a MS-Access DB.
S
secretagentman
Guest
I did, and the technical support person directed me to fix the problem by looking in Microsoft's Knowledge base.
Basically, technical support said look at the IIS5.0 fix in MS KB, but I'm running Windows 2003 Web Editition (IIS 6.0).
I've put my rants about that in another topic. Just search for secretagentman (if possible) or Windows 2003.
Basically, technical support said look at the IIS5.0 fix in MS KB, but I'm running Windows 2003 Web Editition (IIS 6.0).
I've put my rants about that in another topic. Just search for secretagentman (if possible) or Windows 2003.
Similar threads
