Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Can't access Web UI from VM and I'm have no idea about networking

Featured Replies

Everything was working fine. Turned the server off to switch a hard drive for a larger one and now I can't access the Web UI or ping the server from inside a VM.

 

My local network is 192.168.1.0/24. Unraid server is at 192.168.1.3 and the VM is 192.168.1.21.

 

The VM uses vhost0, which I don't know what it means. I also don't understand what virbr0 or docker0 are.

 

Attached is my routing table.

 

br-4ea9173f4445 I guess is a custom docker network I created because I otherwise couldn't make the containers reach each other. I named it "dockernet" don't know why it has a weird name in the routing table. And I don't have "preserve custom networks" enabled, but it doesn't get deleted. I'm afraid to enable it.

 

I've read some posts about adding a route from 192.168.1.0/24 to vhost0, but when I add it nothing changes. The routing table stays the same.

 

Can somebody help me?

Screenshot_20240911-184421-223.png

Solved by Veah

  • Community Expert

Diagnostics

Attach those for best results.

  • Community Expert
  • Solution

Looks like Bridging is off.  Turn that on under network settings.  Suggest also disable Bonding unless you have a specific reason to use it.

  • Author

Cannot do it right now because the data rebuild from the drive swap is still going. But will try. Although I think I disabled bridging myself like a month or two ago, when I updated to 6.12.6 and the "fix common problems" plugin told me to because it was the recommended macvlan configuration for docker or something like that.

 

The bonding being enabled... I do think it's useless because I have a single ethernet connection (that's what it is for, right? to use multiple ethernet connections as if it was a single one) but I've had it enabled since day one years ago. So like I have "preserve custom networks" disabled even though I have a custom docker network. I'm afraid to touch it because it works (or was working, at least). What do I get by disabling bonding? Any performance improvement or lower use of resources?

  • Community Expert

Your understanding of bonding is correct.  It combines multiple network connections to a single bigger one.  If you run only 1 nic, it is useless.  Turn it off.  It is just an extra cog in the machine that can break.

  • Author

So I enabled bridging, disabled bonding and enabled "preserve custom networks" because I felt brave. But now I have the "Fix Common Problems" plugin mentioning the error "Macvlan and Bridging found" and pointing me to this page. Which is what happened months ago and I disabled bridging because of it.

  • Community Expert

The latest stable version has corrected some macvlan problems.  You can update to that or alternatively, change over to ipvlan 

  • Community Expert

 That change is found under settings > docker.

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.