只能通过本地主机访问站点
使用 Plesk 9 拥有一个 Windows VPS。
直到今天我一直在使用 http://myIPaddress:8443 方法访问 Plesk Panel 但现在无法通过浏览器访问。
这是 Google Chrome 错误（错误 101 (net::ERR_CONNECTION_RESET)：未知错误）。
如果我使用 RDC 连接并打开浏览器窗口并通过 http://localhost:8443 连接，它工作得很好。
可能出了什么问题？
Have a have a Windows VPS using Plesk 9.
Until today I have been using the http://myIPaddress:8443 method of accessing Plesk Panel but now I can't access via a browser.
This is the Google Chrome error (Error 101 (net::ERR_CONNECTION_RESET): Unknown error).
If I use an RDC connection and open a browser window and connect via http://localhost:8443 it works just fine.
What could have gone wrong?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
ERR_CONNECTION_RESET 表示您的浏览器和服务器之间的通信被切断，实际上，您的浏览器正在询问服务器“怎么了！”在您的服务器做出响应之前，通信就会中断。
这可能有几件事。它可能是您服务器上的防火墙。它可能是您的互联网连接和/或 PC 上的防火墙，也可能是您的 ISP 本身。
如果您有能力尝试不同的 ISP（甚至可能来自不同的 PC，例如网吧）来测试它是否不在您这边，您几乎可以立即消除 PC 或您自己的网络上的任何软件。
使用 RDP 并能够访问服务器上的 Plesk 安装表明没有任何问题，这可能只是您安装的一个软件或您意外更改的设置一样简单。 （Peerblock 有时会阻止合法的通信）
您可以检查的最后一件事是（如果您正在运行 IIS，我假设您正在运行）检查网站设置，该安装允许哪些 IP 地址。它可能被设置为 127.0.0.1，默认情况下，如果我是你，我会保留它监听所有 IP 地址。
否则，如果您从不同的 ISP 和计算机检查后仍然无法访问它，我建议您向托管公司提交支持票以仔细检查安装。
The ERR_CONNECTION_RESET indicates that the communication between your browser and your server is cut short, in effect, your browser is asking your server "What's up!" and before your server can respond, the communication drops.
This can be several things. It could be the firewall on your server. It could be a firewall on your internet connection and/or PC or it could be your ISP itself.
If you have the ability to try a different ISP (maybe even from a different PC, like an internet cafe) to test that it's not on your end, you can eliminate any software on your PC or your own network from this almost instantly.
Using RDP and being able to access your Plesk installation on the server itself indicates that there's nothing wrong, it could be as simple as just a piece of software you installed or setting you changed by accident. (Peerblock sometimes block's communication that's legitimate)
The last thing you can check is (if you're running IIS, which I assume you are) to check on the website settings which IP addresses, for that installation, is allowed. It could be that it's set to 127.0.0.1, by default I'd keep it to listen on all IP addresses if I were you.
Otherwise, if you've checked from a different ISP and computer and you're still not able to access it, I'd recommend submitting a support ticket with your hosting company to double check the installation.