Cannot access server through network any longer


Recommended Posts

So the other evening I had a weird issue, I could no longer access the server via My Usual method 192.168.1.xx. Which up until that evening had been working fine. I finally was able to access the server via, "Towerx2/login" for some odd reason. This method had been unworking up until this happened. Then all of a sudden today I am unable to access the server via either of those methods. I can still access via monitor and keyboard hooked up to server but gui seems to be not working with this method as well.

 

Sometimes Im getting this when I try and login and sometimes nothing at all

Welcome to our server

The website is currently being setup under this address.

For help and support, please contact: [email protected]

Link to comment

One would think this but I can see the ip address of the server in my router which I have manually configured months ago and im going right to that ip...

 

Also I had been using this same method for months now and use a bookmark so nothing changed there either...Im baffled

 

I can access all my files via network on windows still without issues

Link to comment
1 hour ago, Liquidbings said:

My Usual method 192.168.1.xx

There isn't really any need to anonymize local IP addresses, and I can see your server IP in the diagnostics anyway.

 

Are you sure you are using the correct IP? Your server is set to use DHCP so unless you have its IP reserved by MAC address in your router (what I recommend) then something else on your network may have the IP you are expecting to use.

Link to comment

I'm using mode 5 and I don't get that warning. You are using mode 4

Quote

Mode 4 (802.3ad)
This mode is known as Dynamic Link Aggregation. It creates aggregation groups that share the same speed and duplex settings. It requires a switch that supports IEEE 802.3ad dynamic link. Slave selection for outgoing traffic is done according to the transmit hash policy, which may be changed from the default simple XOR policy via the xmit_hash_policy option. Note that not all transmit policies may be 802.3ad compliant, particularly in regards to the packet mis-ordering requirements of section 43.2.4 of the 802.3ad standard. Different peer implementations will have varying tolerances for noncompliance.

 

Link to comment

Complex bonding has been there since the server was built. Its just the 2 gig ports bonded and has been working fine. I have gotten that warning many times with no issues. The Ip has been always set by to 192.168.1.25 by mac address in the router and I am definitely trying to go directly to that address.

 

Looking through the log with my severe lack of knowledge, would nginx not being able to start because of things already on the port be possibly causing some of the issues?

 

Quote

Sep 21 18:01:57 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:57 TowerX2 root: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:57 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:01:57 TowerX2 root: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:01:57 TowerX2 avahi-daemon[14882]: Joining mDNS multicast group on interface br-677692e79d66.IPv6 with address fe80::42:88ff:fe6a:2caa.
Sep 21 18:01:57 TowerX2 avahi-daemon[14882]: New relevant interface br-677692e79d66.IPv6 for mDNS.
Sep 21 18:01:57 TowerX2 avahi-daemon[14882]: Registering new address record for fe80::42:88ff:fe6a:2caa on br-677692e79d66.*.
Sep 21 18:01:58 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:58 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:01:58 TowerX2 root: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:58 TowerX2 root: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:01:58 TowerX2 avahi-daemon[14882]: Joining mDNS multicast group on interface vethe375a05.IPv6 with address fe80::6c79:39ff:fe70:e916.
Sep 21 18:01:58 TowerX2 avahi-daemon[14882]: New relevant interface vethe375a05.IPv6 for mDNS.
Sep 21 18:01:58 TowerX2 avahi-daemon[14882]: Registering new address record for fe80::6c79:39ff:fe70:e916 on vethe375a05.*.
Sep 21 18:01:58 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:58 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:01:58 TowerX2 root: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:58 TowerX2 root: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:01:59 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:59 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:01:59 TowerX2 root: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:59 TowerX2 root: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:01:59 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:59 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:01:59 TowerX2 root: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Sep 21 18:01:59 TowerX2 root: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Sep 21 18:02:00 TowerX2 nginx: 2021/09/21 18:01:57 [emerg] 17632#17632: still could not bind()
Sep 21 18:02:00 TowerX2 root: nginx: [emerg] still could not bind()

 

Edited by Liquidbings
Link to comment

Not at exactly the same time but around then yes...Thinking about it it may have been after a restart happened so whatever got messed up might have been at the time of changing some of the ports etc on those containers but not actually implemented until the restart took place

 

I just removed those 2 dockers via command line and am rebooting to see if that has any effect

 

Edit: Well that did nothing still not able to access still same issue in log

 

But no welcome to our web server messages now

Edited by Liquidbings
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.