Connection refused

Hello,

I have a problem with my Open Media Vault server which has been running very well for many months. For a few hours now, I can't access Portainer, Plex or any other app. My browser always tells me that my IP "does not allow connection". From my Plex account I can see that access to the server is cut off.

I still have access to the OMV web interface, I can connect via SSH or access via SMB. After some research, I can't find a solution to my problem.

A little more information. I don't know exactly what time the problem appeared but it must be today. However, I made updates from the OMV interface, via the Update Manager. I think that the problem may come from this update ?

Another thing I just noticed, my logs show an error: postfix/postdrop: warning: unable to look up public/pickup: No such file or directory.

I tried a "postfix check" command and the result is : "warning: /var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ"

Does anyone have a solution to propose to solve it? It would be a great help

Hello and thank you for your answer

I have read this thread but I still don't have an effective solution to my problem. If I go back to the events, here is what happened:

- I did the OMV update and lost access to my containers.

- At the same time, I realized that I had a DNS configuration problem (no idea why something moved at this level).

- I fixed my DNS problem and installed app-armor

- I got access to my containers and portainer again.

- However, my containers were only accessible from my local network. For example, I could not access Plex from outside my network.

- In my desperation I tried to update Portainer from the OMV interface, but new drama, Portainer seems to have been uninstalled. The button to access the Portainer interface from OMV-Extras is now grayed out.

- I tried to reinstall Portainer from OMV-Extras but I get the following error:

No portainer containers or images to remove.

Pulling and starting portainer/portainer-ce...

Something went wrong trying to pull and start portainer...

- I can't use the button to remove portainer either, since it tells me in this case that I can't find a portainer container.

If you have any idea how to get access to Portainer in the first place, I'm interested

I tried to follow what is indicated in post 9 but it does not change anything to my problem, I always have the following error when I try to reinstall portainer from OMV-Extras:

No portainer containers or images to remove.
Pulling and starting portainer/portainer-ce ...
Something went wrong trying to pull and start portainer ...

I just tried it and the result is:

Unable to locate the package portainer

Docker is running well. Here is the result of the "systemctl status docker" command line :

docker.service - Docker Application Container Engine

Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)

Active: active (running) since Wed 2023-03-01 17:26:47 CET; 30min ago

Also, i can access (only from my local network) all my others container like Plex or NetData.

Oh, and other information, I'm not running OMV 6 at the moment, I'm on OMV 5. Don't know if upgrading to OMV 6 can help

Ok, I just tried with

omv-release-upgrade

...and there is another error :

Err:12 http://packages.openmediavault.org/public usul Release

Cannot initiate the connection to packages.openmediavault.org:80 (178.254.11.33). - connect (101: Network is unreachable)

Get:13 https://download.docker.com/linux/debian buster InRelease [54.0 kB]

Get:14 https://openmediavault-plugin-developers.github.io/packages/debian usul InRelease [3928 B]

Get:15 https://openmediavault-plugin-developers.github.io/packages/debian usul-extras InRelease [3918 B]

Get:16 https://openmediavault.github.io/packages usul InRelease [12.7 kB]

Reading package lists... Done

E: The repository 'http://packages.openmediavault.org/public usul Release' no longer has a Release file.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

I unfortunately launched the upgrade before seeing your last message.

It looks like the update was done but I still have an error at the end of the process:

you are using pam_tally or pam_tally2 in your configuration

The pam_tally and pam_tally2 modules have been removed from PAM. You are
using one of these modules in your PAM configuration in /etc/pam.d. You must
remove the uses of these modules before PAM can be upgraded; including these
modules in your PAM configuration after the upgrade will stop users from
being able to log into the system.

Consider the pam_faillock module as a replacement for pam_tally.

dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-9+deb11u1_amd64.deb (--unpack):
 new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libpam-modules_1.4.0-9+deb11u1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I can also no longer access the OMV interface. I get a "403 Forbidden - nginx" error.

I haven't used the omv-upgrade command if that's what you're asking, and I don't have a backup either (yes, I'm stupid sometimes, or too confident).

On the other hand I always have local access to my Plex and NetData containers.

omv-firstaid don't work anymore also.

I thank you very much for your great help and for the time spent. The rest is my fault, I wanted to go too fast.

I'll wait to see if others have an idea to help me

Just another information, don't know if it can help, before trying to upgrade to OMV6 i was on the 5.6.26-1 version.