阅读背景:

在Visual Studio 2017上部署AWS Toolkit breanstalk - 500错误

来源:互联网 

I've recently attempted to reploy a simple .Net Core instance on AWS, using the toolkit, everything suggests it deployed correctly, and the security groups are set correctly...

我最近尝试在AWS上重新部署一个简单的.Net Core实例,使用工具包,一切都表明它已正确部署,安全组设置正确...

Yet I can't RDP to the server or view the .net Core ASP web pages... rather I get a 500 error.

但我不能RDP到服务器或查看.net核心ASP网页...而是我得到500错误。

For those more experienced, I'm wondering what kind of trouble shooting is available.

对于那些经验丰富的人,我想知道什么样的问题可以解决。

1 个解决方案

#1


1  

I resolved the RDP issue by modifying the Security Settings in the EC2 dashboard - find the instance that was set up by beanstalk, then on the EC2 (not ELB) service page, find the Security Group links, and then View Inbound Rules. If you have the most common problem, ELB created your instance and opened port 80 (HTTP) and port 22 (SSH), but nothing else. Edit the rule for the security group, change the port 22 to SSH, and then you should be able to connect. Note, for me I set the security to MyIP, but it means you can only RDP from your "home" network.

我通过修改EC2仪表板中的安全设置解决了RDP问题 - 找到由beanstalk设置的实例,然后在EC2(非ELB)服务页面上找到安全组链接,然后查看入站规则。如果您有最常见的问题,ELB创建了您的实例并打开了端口80(HTTP)和端口22(SSH),但没有别的。编辑安全组的规则,将端口22更改为SSH,然后您应该能够连接。请注意,对我来说,我将安全性设置为MyIP,但这意味着您只能从“家庭”网络获得RDP。

Once you can RDP into the machine, you should be able to get to the logs (inetpub/logs)

一旦你可以RDP进入机器,你应该能够到达日志(inetpub / logs)


分享到: