no connection to Portainer after installation of docker under OMV v5

Zitat von ryecoaaron

On armbian buster images, removing network-manager and then omv-firstaid to setup the network adapter using systemd seems to fix that problem.

I guess I need to try that. I never use the web interface to install it but I don't understand why it doesn't work.

What errors?
I've also created a new script that will install OMV itself if it isn't installed already - https://github.com/OpenMediaVa…-Developers/installScript

I'll double check later this morning when I get home. The script... I was getting the path errors we had discussed in another thread. I don't usually use the web interface either, but since the install command wasn't working... I tried it.

Zitat von KM0201

I was getting the path errors we had discussed in another thread

I guess I should make the new script check the path but I still can't figure out how the path is unset on your system.

Zitat von Huberer

When you follow the guide to install OMV v5 over Debian 10, the error comes when you have to install the (security) key.
It says that gnupg, gnupg1 or gnupg2 is missing. By installing all three (I don’t know which exactly) the error is gone and you can continue with the guide

If you use my new installScript, you won't have to worry about that. It does everything for you. So, you install Debian 10 and just execute the script. You end up with OMV, omv-extras, and flashmemory installed.

The script works great (or I'm assuming so... it's still installing). Couple things though that might get some newer users installing this way.

In the past when installing over Debian... It was (and I think still is) recommended to only install SSH server. If you go this route, you're going to be missing a few dependencies.. wget, sudo, and lsb_release. Even if you're installing as root, sudo will fail with a command not found. I'm assuming you could remove the "sudo" part of the command, but that would still leave the other two.

I'm assuming all of these are installed if you install "Standard System Utilities" and SSH Server.. that said, the matter is easy enough to resolve..

apt install wget lsb-release sudo

and then run the script and it should work just fine. It's still running, but I'll report back if there's any further issues.

Why not install Debian with SSH server and standard system utility?

Zitat von macom

Why not install Debian with SSH server and standard system utility?

That's fine (I'm assuming those 3 things are installed then).. but if you follow the instructions on virtually any thread for installing on Debian... you'll find the instructions are to uncheck everything but SSH server.

Zitat von KM0201

In the past when installing over Debian... It was (and I think still is) recommended to only install SSH server. If you go this route, you're going to be missing a few dependencies.. wget, sudo, and lsb_release. Even if you're installing as root, sudo will fail with a command not found. I'm assuming you could remove the "sudo" part of the command, but that would still leave the other two.

I haven't run into an install where these aren't installed. If wget isn't installed, the command needs to be altered but the script can't install the utility that downloads the script. I added it to the readme.

Zitat von ryecoaaron

I haven't run into an install where these aren't installed. If wget isn't installed, the command needs to be altered but the script can't install the utility that downloads the script. I added it to the readme.

like I said, I think it's because I didn't install system utilities. I imagine if I installed it, those 3 things would have been installed.

@ryecoaaron that should be lsb-release that was a typo on my part

My bad

I thought this would be appropriate here as I have replied to this post before I reinstall I decided to enable cockpit and I was greeted with the same error as portainer.

This site can't be reached -> 192.168.1.50 refused to connect ERR_CONNECTION_REFUSED standard Chrome error message.

Procedure;

OMV-Extras -> Enable Cockpit -> Save -> Waited for it to complete -> Open Cockpit web interface -> above error

SSH into OMV -> systemctl status cockpit -> loaded inactive (dead) -> systemctl start cockpit -> loaded active (running) -> Open Cockpit web interface -> same error

Reboot -> OMV-Extras -> Open Cockpit web interface same error, and yes it is using the ip address port 9090.

This was the exact same error I got when enabled Portianer.

Zitat von geaves

I thought this would be appropriate here as I have replied to this post before I reinstall I decided to enable cockpit and I was greeted with the same error as portainer.

This site can't be reached -> 192.168.1.50 refused to connect ERR_CONNECTION_REFUSED standard Chrome error message.

Procedure;

OMV-Extras -> Enable Cockpit -> Save -> Waited for it to complete -> Open Cockpit web interface -> above error

SSH into OMV -> systemctl status cockpit -> loaded inactive (dead) -> systemctl start cockpit -> loaded active (running) -> Open Cockpit web interface -> same error

Reboot -> OMV-Extras -> Open Cockpit web interface same error, and yes it is using the ip address port 9090.

This was the exact same error I got when enabled Portianer.

Alles anzeigen

Sounds like the other problem I was having... Is your NAS online? When I was having this issue after installing Portainer, my NIC somehow lost it's configuration.

ping aol.com and see if you get a result. My guess is, you're not online. run omv-firstaid and when you configure the NIC, you'll probably see that are two devices there now, one being named "docker0" (that's what it was called on my VM).

Reconfigure your physical NIC, and you should be good.

Zitat von KM0201

ping aol.com and see if you get a result.

Got a result 8 transmitted 8 received so it's online, my nic is configured with a static ip as well.

I get a response doing dig aol.com and dig google.com

Zitat von Huberer

@KM0201

when you do a fresh installation of Debian (I always use the "netinst" version) I always tick "ssh-server" and "standard system utilities". I didn't face any problems by doing that. These two I would always recommend.

I don't dispute that.. but again, if you read virtually all the instructions for installing on top of Debian... for years it's been suggested to only install the SSH server. It didn't cause an issue before... now it obviously does.

Zitat von Huberer

did you do the installation in a VM or on real hardware?

No, real hardware using the iso and not the Debian install.

Zitat von KM0201

that should be lsb-release that was a typo on my part

My bad

No biggie. I should have noticed that too. It is confusing since the command is lsb_release but the package name is lsb-release. Fixed now.

Zitat von Huberer

Thanks for the info. So the issue must be docker and Portainer

For me docker installed, I believe portainer did it just didn't 'activate' or didn't start correctly hence I installed manually. I'm now having the same problem with Cockpit.