Troubleshoot problems while publishing or downloading websites in WebMatrix
This article helps you resolve problems you might face when you publish or download websites in WebMatrix.
Following are the errors that you might see when you publish or download websites:
- "Bad gateway or proxy error"
- "Could not connect to the remote computer"
- "Could not connect to the destination computer"
- "Connected to the remote computer ("computername") using the Web Management Service, but could not authorize"
- "Unable to read beyond the end of the stream"
- "Could not complete the request to remote agent URL"
Bad gateway or proxy error
Cause
A proxy server is most likely blocking access to the server.
Resolution
Try installing your corporation's required firewall client, and disabling all settings in Internet Explorer > Tools > Options > Connections > LAN settings.
Could not connect to the remote compute, Could not connect to the destination computer
The cause and resolution for both these errors are the same.
Cause
The server was contacted but didn't respond to the publishing. This is often due to the Web Management Service not being started on the server.
Resolution
Contact your server administrator or hosting provider.
Connected to the remote computer using the Web Management Service, but could not authorize
Cause
WebMatrix connected to the server, but your user name isn't authorized for the site name.
Resolution
Check the publish settings to verify that your site name is correct. If everything looks correct, contact your server administrator or hosting provider.
Unable to read beyond end of the stream
Cause
Either the server or a device such as a router between your computer and the server closed the connection. This can be due to firewall or server configuration.
Resolution
If you still get this error consistently after several publishing attempts, try when you are connected to another network. If it still occurs, contact your server administrator or hosting provider.
Could not complete the request to remote agent URL
Cause
This is a transient issue when the network is busy.
Resolution
Try publishing the website again. If the error is shown again, contact your server administrator or hosting provider.