We have migrated classic ASP sites to Plesk Parallels on GoDaddy. Because the server is now ASP.NET, we have needed to employ a web.config file.
A basic web.config file is fine enough for the site to run without errors, but whenever we attempt to modify this to raise the 200kb file upload limit (browser-based), the site either crashes or errors on >200kb upload.
Does anyone have any tips or experience with GoDaddy + Plesk + web.config files increasing the max file size? Even a known-working copy of a web.config file in this context would be great.
Sorry if this question is so pedestrian, but thanks in advance!
This might work for other host providers other than GoDaddy but here is the solution in case you are looking for one:
Plesk > Virtual Directories > Directory Properties Tab > Scroll to ASP Settings and override the “Maximum size of entity body of an ASP request (KB)"
primesiteweb.com
Related
I have a number of large sites with thousands of images consuming few gigabytes each. We got a new server and I have to move all these sites there (old server will be decommissioned). What's the best way to do this and what I should be paying attention to?
Old server is Windows 2008 R2 IIS 7.5
New server is Windows 2012 IIS 8.5
I explored few options:
IIS shared configuration - did not work for me for some reason. I got DLL conflict errors saying that some .Net 7.5 module was not found. I guess that means I can export/import configuration only within the same IIS version? not sure. But at the end of the day I had to completely reinstall IIS on my new server - it just would not work after import. So I would not recommend this unless you know what you do.
WebDeploy - I think it could work for me - but due to the huge number of files and site size it was not able to ZIP the sites - or may be i was not patient enough. I guess it would work for smaller sites.
XML export/import - finally, I found this article: it allowed me to export websites & app pool into XML and then import them on the new server. That worked beautifully:
Export
%windir%\system32\inetsrv\appcmd list apppool /config /xml >
c:\apppools.xml
%windir%\system32\inetsrv\appcmd list site /config /xml >
c:\sites.xml
Import
%windir%\system32\inetsrv\appcmd add apppool /in < c:\apppools.xml
%windir%\system32\inetsrv\appcmd add site /in < c:\sites.xml
after that I only had to FTP my files to the new server - and I was good to go!
few things to remember:
Directory structure - keep it the same as on old server - no need to tweak XML files then
HTTPS certificates - don't forget to export them as well
Security - if you have assigned any special permissions to your sites' folders - make sure you re-create them on the new server
Additional IIS modules - like URL Rewrite - itemize and install them
Bindings - if you have wildcard ones, no need to worry but if your sites were bound to an IP address - use search/replace in sites.XML file to update it.
This is very simple to reproduce:
Create a new VM (xtra small in my case, tried both Windows 2012
and 2008R2)
Install IIS using default config.
Create a Web Site using IIS Manager specifying a folder such as
C:\inetpub\simple.
Using Windows Explorer, create a new file called index.txt
Rename the file to index.htm
Edit the file with Notepad to make it a basic but valid html5
document and Save.
From IIS Manager, select the new website and click the Browse
Website link on the right side of the screen.
I get:
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Now look at the Contents of the web site in IIS Manager and you will see that the file has a .txt extension pasted onto the end : index.htm.txt
This does not happen on my local server.
I am new to Azure and probably missing something very basic but right now I feel like I am going insane. Can anyone put me out of my misery?
This is IIS configuration issue, not Azure specific. And I would not even say it is an issue at all.
index.html is not in the list of default documents for IIS. And has never been. index.htm however is. You get 403.14 forbidden, because Directory Browsing is by default forbidden in IIS. Again, absolutely typical IIS configuration which hasn't changed for ages!
Your solutions:
Configure index.html to be in default documents (read how to do this here)
enable directory browsing (read how to do it here)
For the sake of others as stupid as me, this is all down to Windows Explorer configuration. Normally, the first thing that I do with a new Windows install is to turn off 'Hide known filename extensions'. This time I forgot.
Im having some trouble with basic IIS administration. I have created a site at C:\test\ with a document called test.htm. When I browse to testsite/test.htm iis is trowing an error saying it could not access the web.config. But the folder hasnt even got any asp.net resources in it. Whats going on?
I just did the same as you:
Created a new web site on C:\test
Set its binding to port 81 (port 80 already used)
Started the site
Created a html test file test.htm in C:\test
browsed http://localhost:81/test.htm and it worked
BTW - I used IIS 7.5
Is your "testsite" even mapped to the C:\test folder?
If not that would not work. Make sure that the website is mapped to where the files are.
Default folder for the default web site is c:\inetpub\wwwroot
Good luck
hi i am comletly new to iis and asp.net i am trying to setup bugNET on a godaddy server. i created a virtual directory and once i tried to launch the site i get this error:
Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.
here is complete detail of what i did.
hosting: godaddy
created virtual directory (child folder of root) - named: devbunk with these settings (anonymous access, directory browsing)
that is all i can do to with iis on godaddy.
the error tells me that i need to turn the virtual directory as an application. godaddy doesnt let me do that... how do i do it? btw, i have iis7 setup.
You can configure this with Godaddy Hosting Control Center. log in to godaddy hosting center.
Go to Content >> IIS Management.
Click on the pencil icon to edit your selected directory.
you will get a popped up screen with three check boxes. You need to check the one that says "Set Application Root".
Click Ok and your directory will be configured as an application in IIS.
Hope this helps you and feel free to ping me if you need more info.
You need godaddy to do that, usually hosters do offer the ability to convert a regular folder as an application through their Control Panel, so if you have access to one search for that option. Other hosters give access through IIS Manager and Web Deploy to convert folders to applications as well, but it boils down to "you need your hoster to do that".
There are no ways for you to do that through Web.config or FTP or etc. I think Front Page Server Extensions did had a way as well. The best thing is contact your hoster and ask them what is the right way of doing this. Usually all hosters will allow you to create as many applications as you need as long as they run the same .net version.
Check the properties on Web.Config to ensure "Copy to Output Directory" is set to "Do not copy"
I have an issue using cruisecontrol dashboard on a windows server 2008 IIS7 installation.
Even if I use an integrated mode with webserver configuration section, or a classic mode, the dashboard itself will be displayed but any static content, javascript files, images will be displayed.
I don't know if this is an issue or a configuration mistake, I followed the installation procedure, but nothing works about static files.
I've looked for a solution in the iis log file, and I saw the http 200 for each static file.
Any idea?
Thanks
Try using the developer tools for Chrome/Firefox/IE to look at the requests being made for those static items.
Maybe you have your ccnet website on a port but the site makes requests for static items on port 80 by default.
Maybe ccnet is in a subdirectory and the static requests go to the root?
Check that IIS Static Content is enabled:
Go to
Control Panel
Program & Features
Turn Windows features on or off (upper left)
Internet Information Servies/World Wide Web Services/Static Content