BlakeB Posted February 12, 2021 Share Posted February 12, 2021 Everything was working fine for over a year, then there was a FIOS router firmware update and things went south. My main computer is fine, but Unraid hasn't liked it. I've tried everything I can think of, from enabling DMZ, a new USB stick, new DNS and IP, I can't figure out what is going on. I'm still novice to Unraid so I'm sure I'm missing something you guys are more seasoned too. Current logs will show that I'm missing my Plus.key, that's because I just tried swapping the keys and entering the new replacement key, problem now is Unraid is blind to the internet and gets a 504 gateway error. tower-syslog-20210212-2229.zip Quote Link to comment
trurl Posted February 12, 2021 Share Posted February 12, 2021 35 minutes ago, BlakeB said: enabling DMZ Don't put your server on the internet. 38 minutes ago, BlakeB said: missing my Plus.key, that's because I just tried swapping the keys Was there something wrong with your flash drive? Normally you put the old key on the new flash and then use the procedure on the Tools - Registration page. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. Quote Link to comment
BlakeB Posted February 13, 2021 Author Share Posted February 13, 2021 (edited) 1 hour ago, trurl said: Don't put your server on the internet. Was there something wrong with your flash drive? Normally you put the old key on the new flash and then use the procedure on the Tools - Registration page. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. I don't know if there was anything wrong with the flash drive. I was just troubleshooting ideas, so I got another drive to test. I just wasn't sure what else would start blocking UnRaid from reaching outside of my network. I can't ping outside networks, and this is what I get when I try to install the new key. Sorry, here is the Diag file. Thought I attached it before. tower-diagnostics-20210212-1924.zip Edited February 13, 2021 by BlakeB Quote Link to comment
Squid Posted February 13, 2021 Share Posted February 13, 2021 Feb 12 16:11:16 Tower in.telnetd[22117]: connect from 117.192.88.101 (117.192.88.101) Unless you're living in India, with an alter-ego living in the US and China (simultaneously), then 1 hour ago, trurl said: Don't put your server on the internet. Remove it from the DMZ Quote Link to comment
BlakeB Posted February 13, 2021 Author Share Posted February 13, 2021 3 minutes ago, Squid said: Feb 12 16:11:16 Tower in.telnetd[22117]: connect from 117.192.88.101 (117.192.88.101) Unless you're living in India, with an alter-ego living in the US and China (simultaneously), then Remove it from the DMZ The DMZ was just spitballing a way to see if the router was blocking its access. I don't think it's that. Quote Link to comment
Squid Posted February 13, 2021 Share Posted February 13, 2021 1 minute ago, BlakeB said: The DMZ was just spitballing a way to see if the router was blocking its access. I don't think it's that. Neither do I, but if your comfortable with attempts to log in from everywhere in the world, then it's no skin off my back. You should try setting static DNS addresses within Settings - Network settings. Quote Link to comment
BlakeB Posted February 13, 2021 Author Share Posted February 13, 2021 3 minutes ago, Squid said: Neither do I, but if your comfortable with attempts to log in from everywhere in the world, then it's no skin off my back. You should try setting static DNS addresses within Settings - Network settings. Same thing. It was set static in the past before the IP change. Quote Link to comment
strike Posted February 13, 2021 Share Posted February 13, 2021 Try setting the DNS server 1 to 1.1.1.1 ,server 2 to 1.0.0.1 and server 3 to 192.168.1.1 Quote Link to comment
BlakeB Posted February 13, 2021 Author Share Posted February 13, 2021 4 minutes ago, strike said: Try setting the DNS server 1 to 1.1.1.1 ,server 2 to 1.0.0.1 and server 3 to 192.168.1.1 Nothing, same result. Quote Link to comment
trurl Posted February 13, 2021 Share Posted February 13, 2021 1 hour ago, BlakeB said: The DMZ was just spitballing a way to see if the router was blocking its access. I don't think it's that. So did you? 1 hour ago, Squid said: Remove it from the DMZ Seriously, the bots found you immediately and not just India. They are bots and will attack repeatedly and relentlessly. Feb 12 14:35:00 Tower in.telnetd[4568]: connect from 183.171.198.27 (183.171.198.27) Feb 12 14:40:44 Tower in.telnetd[19067]: connect from 93.148.246.198 (93.148.246.198) Feb 12 14:43:01 Tower sshd[24810]: Invalid user admin from 77.247.181.165 port 1230 Feb 12 14:43:04 Tower sshd[24894]: Invalid user admin from 104.244.73.205 port 38237 Feb 12 14:47:41 Tower sshd[3754]: Invalid user user from 128.199.206.22 port 56242 Feb 12 14:52:51 Tower in.telnetd[17287]: connect from 212.210.173.74 (212.210.173.74) Feb 12 15:06:23 Tower in.telnetd[19088]: connect from 172.251.43.127 (172.251.43.127) Feb 12 15:39:21 Tower in.telnetd[5546]: connect from 108.6.48.190 (108.6.48.190) Feb 12 15:53:18 Tower sshd[8503]: Failed password for root from 174.138.15.47 port 47416 ssh2 Feb 12 15:53:20 Tower in.telnetd[8673]: connect from 117.192.88.101 (117.192.88.101) Feb 12 15:54:36 Tower in.telnetd[11862]: connect from 42.192.161.117 (42.192.161.117) Feb 12 16:08:23 Tower in.telnetd[14800]: connect from 103.121.234.144 (103.121.234.144) Feb 12 16:08:43 Tower in.telnetd[15657]: connect from 104.178.219.195 (104.178.219.195) Feb 12 16:17:17 Tower in.telnetd[5035]: connect from 179.96.241.235 (179.96.241.235) https://www.abuseipdb.com/check/183.171.198.27 Malaysia https://www.abuseipdb.com/check/93.148.246.198 Italy https://www.abuseipdb.com/check/77.247.181.165 Netherlands https://www.abuseipdb.com/check/104.244.73.205 Luxembourg https://www.abuseipdb.com/check/128.199.206.22 Singapore https://www.abuseipdb.com/check/212.210.173.74 Italy https://www.abuseipdb.com/check/172.251.43.127 United States of America https://www.abuseipdb.com/check/108.6.48.190 United States of America https://www.abuseipdb.com/check/174.138.15.47 Netherlands https://www.abuseipdb.com/check/117.192.88.101 India https://www.abuseipdb.com/check/42.192.161.117 China https://www.abuseipdb.com/check/103.121.234.144 India https://www.abuseipdb.com/check/104.178.219.195 United States of America https://www.abuseipdb.com/check/179.96.241.235 Brazil And no doubt others since then if your server is still on the internet. Quote Link to comment
BlakeB Posted February 13, 2021 Author Share Posted February 13, 2021 13 minutes ago, trurl said: So did you? Seriously, the bots found you immediately and not just India. They are bots and will attack repeatedly and relentlessly. Feb 12 14:35:00 Tower in.telnetd[4568]: connect from 183.171.198.27 (183.171.198.27) Feb 12 14:40:44 Tower in.telnetd[19067]: connect from 93.148.246.198 (93.148.246.198) Feb 12 14:43:01 Tower sshd[24810]: Invalid user admin from 77.247.181.165 port 1230 Feb 12 14:43:04 Tower sshd[24894]: Invalid user admin from 104.244.73.205 port 38237 Feb 12 14:47:41 Tower sshd[3754]: Invalid user user from 128.199.206.22 port 56242 Feb 12 14:52:51 Tower in.telnetd[17287]: connect from 212.210.173.74 (212.210.173.74) Feb 12 15:06:23 Tower in.telnetd[19088]: connect from 172.251.43.127 (172.251.43.127) Feb 12 15:39:21 Tower in.telnetd[5546]: connect from 108.6.48.190 (108.6.48.190) Feb 12 15:53:18 Tower sshd[8503]: Failed password for root from 174.138.15.47 port 47416 ssh2 Feb 12 15:53:20 Tower in.telnetd[8673]: connect from 117.192.88.101 (117.192.88.101) Feb 12 15:54:36 Tower in.telnetd[11862]: connect from 42.192.161.117 (42.192.161.117) Feb 12 16:08:23 Tower in.telnetd[14800]: connect from 103.121.234.144 (103.121.234.144) Feb 12 16:08:43 Tower in.telnetd[15657]: connect from 104.178.219.195 (104.178.219.195) Feb 12 16:17:17 Tower in.telnetd[5035]: connect from 179.96.241.235 (179.96.241.235) https://www.abuseipdb.com/check/183.171.198.27 Malaysia https://www.abuseipdb.com/check/93.148.246.198 Italy https://www.abuseipdb.com/check/77.247.181.165 Netherlands https://www.abuseipdb.com/check/104.244.73.205 Luxembourg https://www.abuseipdb.com/check/128.199.206.22 Singapore https://www.abuseipdb.com/check/212.210.173.74 Italy https://www.abuseipdb.com/check/172.251.43.127 United States of America https://www.abuseipdb.com/check/108.6.48.190 United States of America https://www.abuseipdb.com/check/174.138.15.47 Netherlands https://www.abuseipdb.com/check/117.192.88.101 India https://www.abuseipdb.com/check/42.192.161.117 China https://www.abuseipdb.com/check/103.121.234.144 India https://www.abuseipdb.com/check/104.178.219.195 United States of America https://www.abuseipdb.com/check/179.96.241.235 Brazil And no doubt others since then if your server is still on the internet. Nice, A Verizon tech in India for my router is the one that even suggested enabling DMZ when this all started. I disabled it a few hours ago. Should I just force an IP reset at this point? 27 minutes ago, strike said: Try setting the DNS server 1 to 1.1.1.1 ,server 2 to 1.0.0.1 and server 3 to 192.168.1.1 Nothing, same result. Quote Link to comment
trurl Posted February 14, 2021 Share Posted February 14, 2021 On 2/12/2021 at 9:24 PM, BlakeB said: Verizon tech in India for my router is the one that even suggested enabling DMZ Maybe they thought what you were putting on the internet was secure for that purpose, or just unimportant. Quote Link to comment
BlakeB Posted February 14, 2021 Author Share Posted February 14, 2021 Ended up doing a factory reset on the router after leaving it unplugged for 24 hours. New external IP and looks like I can access the internet in Unraid again. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.