Report post

Security image * Required field


This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param="New Setup - Digital Ocean Droplet"]318[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><comcode-quote param="2"><comcode-quote param="Hawkeye">After about 10 or 15 pings, the IP stopped responding. No pings, ssh or stream commands will work. Per our earlier discussion, I deliberately did not create a firewall for the droplet at Digital Ocean.<br />I have rebooted the droplet to no avail. I have contacted their tech support but have not received a reply yet.<br />My questions are as follows, it appears that some kind of threshold has been met and the IP is no longer accepting incoming connection requests. Does Digital Ocean have their own firewall that is in place, or is this something that is built into NGINX? How can I increase the threshold limit?<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]317[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />DigitalOcean certainly does not have any sort of firewall that would block a ping.<br />I assume that you rebooted the droplet by power off & back on through the DigitalOcean web interface. Do you see any stats on their interface about system resource usage?<br />There is no "threshold limit" built into NGINX to my knowledge. Even if some sort of threshold for maximum connections had been met somewhere on your system, there should be no active connections after rebooting your droplet, so you should still be able to connect again.<br />Possible reasons for not being able to SSH into a droplet include the SSH daemon being stopped or the system's resources being tied up. Seeing as you can't ping either, I would assume it's a resource issue, unless there is a firewall in play somewhere (once again, that would be something you set up on your droplet, as DigitalOcean won't be blocking pings, certainly not by default.)<br />Hypothetically, if you had something in your NGINX configuration or your Bash script that completely tied up your system's resources, and NGINX and/or your Bash script were set to start up automatically with your system (e.g. with Systemd/your init), I could imagine your droplet booting up, the script/NGINX being started, and the system immediately (and automatically) being tied up, not allowing you to connect any more.<br />I usually use Linode these days, but I recall that DigitalOcean had a web-based console that you can access through your web browser. That web-based console would give you a "direct" connection into your droplet's TTY (they're able to provide this cheaply because the droplet is actually a VM). Are you able to access the web console? Watching the machine boot up/trying to connect through the web/"physical" console and trying to stop whatever process is crashing the system before it starts would be my next step if that's what is happening.<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color This is a reported post for a post in the topic [post param="New Setup - Digital Ocean Droplet"]318[/post], by jacobgkau [quote="2"] [quote="Hawkeye"] After about 10 or 15 pings, the IP stopped responding. No pings, ssh or stream commands will work. Per our earlier discussion, I deliberately did not create a firewall for the droplet at Digital Ocean. I have rebooted the droplet to no avail. I have contacted their tech support but have not received a reply yet. My questions are as follows, it appears that some kind of threshold has been met and the IP is no longer accepting incoming connection requests. Does Digital Ocean have their own firewall that is in place, or is this something that is built into NGINX? How can I increase the threshold limit? [snapback]317[/snapback][/quote] DigitalOcean certainly does not have any sort of firewall that would block a ping. I assume that you rebooted the droplet by power off & back on through the DigitalOcean web interface. Do you see any stats on their interface about system resource usage? There is no "threshold limit" built into NGINX to my knowledge. Even if some sort of threshold for maximum connections had been met somewhere on your system, there should be no active connections after rebooting your droplet, so you should still be able to connect again. Possible reasons for not being able to SSH into a droplet include the SSH daemon being stopped or the system's resources being tied up. Seeing as you can't ping either, I would assume it's a resource issue, unless there is a firewall in play somewhere (once again, that would be something you set up on your droplet, as DigitalOcean won't be blocking pings, certainly not by default.) Hypothetically, if you had something in your NGINX configuration or your Bash script that completely tied up your system's resources, and NGINX and/or your Bash script were set to start up automatically with your system (e.g. with Systemd/your init), I could imagine your droplet booting up, the script/NGINX being started, and the system immediately (and automatically) being tied up, not allowing you to connect any more. I usually use Linode these days, but I recall that DigitalOcean had a web-based console that you can access through your web browser. That web-based console would give you a "direct" connection into your droplet's TTY (they're able to provide this cheaply because the droplet is actually a VM). Are you able to access the web console? Watching the machine boot up/trying to connect through the web/"physical" console and trying to stop whatever process is crashing the system before it starts would be my next step if that's what is happening. [/quote] //// PUT YOUR REPORT BELOW \\\\ Use of this website implies that you agree to the website rules and privacy policy.

Security image * Required field

This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param=&quot;New Setup - Digital Ocean Droplet&quot;]318[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><comcode-quote param="2"><comcode-quote param="Hawkeye">After about 10 or 15 pings, the IP stopped responding. No pings, ssh or stream commands will work. Per our earlier discussion, I deliberately did not create a firewall for the droplet at Digital Ocean.<br />I have rebooted the droplet to no avail. I have contacted their tech support but have not received a reply yet.<br />My questions are as follows, it appears that some kind of threshold has been met and the IP is no longer accepting incoming connection requests. Does Digital Ocean have their own firewall that is in place, or is this something that is built into NGINX? How can I increase the threshold limit?<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]317[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />DigitalOcean certainly does not have any sort of firewall that would block a ping.<br />I assume that you rebooted the droplet by power off &amp; back on through the DigitalOcean web interface. Do you see any stats on their interface about system resource usage?<br />There is no &quot;threshold limit&quot; built into NGINX to my knowledge. Even if some sort of threshold for maximum connections had been met somewhere on your system, there should be no active connections after rebooting your droplet, so you should still be able to connect again.<br />Possible reasons for not being able to SSH into a droplet include the SSH daemon being stopped or the system&#039;s resources being tied up. Seeing as you can&#039;t ping either, I would assume it&#039;s a resource issue, unless there is a firewall in play somewhere (once again, that would be something you set up on your droplet, as DigitalOcean won&#039;t be blocking pings, certainly not by default.)<br />Hypothetically, if you had something in your NGINX configuration or your Bash script that completely tied up your system&#039;s resources, and NGINX and/or your Bash script were set to start up automatically with your system (e.g. with Systemd/your init), I could imagine your droplet booting up, the script/NGINX being started, and the system immediately (and automatically) being tied up, not allowing you to connect any more.<br />I usually use Linode these days, but I recall that DigitalOcean had a web-based console that you can access through your web browser. That web-based console would give you a &quot;direct&quot; connection into your droplet&#039;s TTY (they&#039;re able to provide this cheaply because the droplet is actually a VM). Are you able to access the web console? Watching the machine boot up/trying to connect through the web/&quot;physical&quot; console and trying to stop whatever process is crashing the system before it starts would be my next step if that&#039;s what is happening.<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br />

This is a reported post for a post in the topic [post param="New Setup - Digital Ocean Droplet"]318[/post], by jacobgkau

[quote="2"]
[quote="Hawkeye"]
After about 10 or 15 pings, the IP stopped responding. No pings, ssh or stream commands will work. Per our earlier discussion, I deliberately did not create a firewall for the droplet at Digital Ocean.
I have rebooted the droplet to no avail. I have contacted their tech support but have not received a reply yet.
My questions are as follows, it appears that some kind of threshold has been met and the IP is no longer accepting incoming connection requests. Does Digital Ocean have their own firewall that is in place, or is this something that is built into NGINX? How can I increase the threshold limit?
[snapback]317[/snapback][/quote]

DigitalOcean certainly does not have any sort of firewall that would block a ping.
I assume that you rebooted the droplet by power off & back on through the DigitalOcean web interface. Do you see any stats on their interface about system resource usage?
There is no "threshold limit" built into NGINX to my knowledge. Even if some sort of threshold for maximum connections had been met somewhere on your system, there should be no active connections after rebooting your droplet, so you should still be able to connect again.
Possible reasons for not being able to SSH into a droplet include the SSH daemon being stopped or the system's resources being tied up. Seeing as you can't ping either, I would assume it's a resource issue, unless there is a firewall in play somewhere (once again, that would be something you set up on your droplet, as DigitalOcean won't be blocking pings, certainly not by default.)
Hypothetically, if you had something in your NGINX configuration or your Bash script that completely tied up your system's resources, and NGINX and/or your Bash script were set to start up automatically with your system (e.g. with Systemd/your init), I could imagine your droplet booting up, the script/NGINX being started, and the system immediately (and automatically) being tied up, not allowing you to connect any more.
I usually use Linode these days, but I recall that DigitalOcean had a web-based console that you can access through your web browser. That web-based console would give you a "direct" connection into your droplet's TTY (they're able to provide this cheaply because the droplet is actually a VM). Are you able to access the web console? Watching the machine boot up/trying to connect through the web/"physical" console and trying to stop whatever process is crashing the system before it starts would be my next step if that's what is happening.
[/quote]

//// PUT YOUR REPORT BELOW \\\\

Use of this website implies that you agree to the website rules and privacy policy.

Statistics