CodePudding user response:
Look at the nginx logCodePudding user response:
80/8080/port 443 ICP registration is needed to use, you can try the other very use port, such as 8081,CodePudding user response:
EC2 is variable IP or the EIP, if is variable IP, IP changed after restart, you have to look at the IP again, had better use the EIPCodePudding user response:
EC2 host domain name should be used to accessCodePudding user response:
First suggested using the EIP instead of create EC2 is AWS automatically assigned public IP, or you shut the EC2 and then start the public IP will change, restart the public IP is the same, then close the EC2 host the source and target check, right-click on the instance - & gt; Networking - & gt; Change the source and target checkCodePudding user response:
This phenomenon is a little strangeIf the EIP is not set, then restart with the original public IP could not access (IP will change), but is not in conformity with the LZ said that can be accessed after the restart, so LZ may use EIP is
Problem is access to the display for several minutes, not line, nginx is no exception, and there has been a remote SSH from LZ screenshots, EC2 didn't also goes down, and the inbound security group is no problem, it was kind of strange
2 l said ICP for the record, like cloud9 this limitation (I use cloud9 met), general ec2 like this not limited (myself in ec2 nginx no problem, that is, port 80)
What is the local network proxy agent such as what is the problem?
CodePudding user response:
Can try the machine do you have any questions or Intranet access port 80Is excluded under the machine service issues, or the network of network problems