New install, installing packages or checking for updates fails
We're having some issues with a new installation of Umbraco 7.5.9 on Windows Server 2008R2 (so IIS version 7.5). We've noticed the following issues:
Checking for updates fails
Installing Umbraco Forms fails
Installing a package (e.g. a starter website) fails
The logs for each of these actions show the following :
System.Net.WebException: The request failed with HTTP status 403: Forbidden.
We've checked the permissions on the folder that Umbraco has been installed into: IUSR and IIS_IUSRS and the ApplicationPoolIdentity have been given modify access.
We've also disabled Internet Explorer Enhanced Security Configuration in case that was causing an issue.
It looks like an issue where Umbraco or .Net cannot make web service requests for some reason. Any suggestions as to where we should look to start debugging and resolving this would be very welcome. Thanks
Thanks for the suggestion. Opening IE on the server desktop and browsing to that page works fine, no TCP errors.
Other things we've tried to get this working is disabling the firewall and confirming there is no proxy server requirement for internet access.
When we try the Health Check in Developer settings, (when logged into Umbraco) the 'Click-Jacking Protection' test returns 'Error pinging the URL http://www.my-new-website.test:80 - 'The remote server returned an error: (403) Forbidden.' ' This is baffling because http://www.my-new-website.test:80 is of course itself and this URL works in the web browser on the server desktop.
It seems that .Net simply does not have any network access for some reason. We also run java code on this server which has no problem making internet connections. Is there some very simple .Net network access code we could run that could narrow down the problem? At this point we'll try anything to get this working so any suggestions are welcome.
In case anyone else comes accross this, it remains unsolved. However it was an issue with our development system rather than any fault of Umbraco.
We deployed Umbraco to a different server following the same steps and it all works perfectly.
New install, installing packages or checking for updates fails
We're having some issues with a new installation of Umbraco 7.5.9 on Windows Server 2008R2 (so IIS version 7.5). We've noticed the following issues:
The logs for each of these actions show the following :
System.Net.WebException: The request failed with HTTP status 403: Forbidden.
We've checked the permissions on the folder that Umbraco has been installed into: IUSR and IIS_IUSRS and the ApplicationPoolIdentity have been given modify access. We've also disabled Internet Explorer Enhanced Security Configuration in case that was causing an issue.
It looks like an issue where Umbraco or .Net cannot make web service requests for some reason. Any suggestions as to where we should look to start debugging and resolving this would be very welcome. Thanks
Hi,
Try logging onto the 2008R2 server and browsing to this page
Can you see it or do you get a message telling you to turn on TLS?
If you get the TLS message then there's your problem. Google will give plenty of suggestions of how to fix it, here is one
Tim
Hi Tim,
Thanks for the suggestion. Opening IE on the server desktop and browsing to that page works fine, no TCP errors. Other things we've tried to get this working is disabling the firewall and confirming there is no proxy server requirement for internet access.
When we try the Health Check in Developer settings, (when logged into Umbraco) the 'Click-Jacking Protection' test returns 'Error pinging the URL http://www.my-new-website.test:80 - 'The remote server returned an error: (403) Forbidden.' ' This is baffling because http://www.my-new-website.test:80 is of course itself and this URL works in the web browser on the server desktop.
It seems that .Net simply does not have any network access for some reason. We also run java code on this server which has no problem making internet connections. Is there some very simple .Net network access code we could run that could narrow down the problem? At this point we'll try anything to get this working so any suggestions are welcome.
In case anyone else comes accross this, it remains unsolved. However it was an issue with our development system rather than any fault of Umbraco. We deployed Umbraco to a different server following the same steps and it all works perfectly.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.