Please help!! no access to OMV WebGUI nginx 503 service temporarily unavailable

Zitat von Zoki

You can not instoll nor update, as your DNS is borked.

Post the output of the commands I posted before.

root@openmediavault:~# ls -l /run/systemd/resolve/resolv.conf
ls: cannot access '/run/systemd/resolve/resolv.conf': No such file or directory
root@openmediavault:~# cat /run/systemd/resolve/resolv.conf
cat: /run/systemd/resolve/resolv.conf: No such file or directory
root@openmediavault:~#

I had OMV4 for quite a while and tried installing Nextcloud but couldn't get it working and gave up. Then I got back into it and updated to OMV5. That wasn't fun. I followed Techno Dad Life's videos and got it updated. I messed OMV up a few times trying to get external access but was able to restore it. Or so I thought...

All of this has happened over time, so it's hard to remember exact steps that I've taken.

ok, now systemctl status systemd-resolved.service

And please tell me how did you install OMV and what did you install thereafter?

A workaround to get you onto the internat again would be to delete /etc/resolv.conf and re-create the file with this content:

nameserver 8.8.8.8

But after this you have to get systemd-resolvd to work.

Zoki

Read back posts #46, 47, 48.

It seems atoddvr6 is behind a CGNAT (whatever that is) if it makes any difference.

As I see it, DNS resolve should always work.

Zitat von Zoki

ok, now systemctl status systemd-resolved.service

And please tell me how did you install OMV and what did you install thereafter?

A workaround to get you onto the internat again would be to delete /etc/resolv.conf and re-create the file with this content:

Code

nameserver 8.8.8.8

But after this you have to get systemd-resolvd to work.

root@openmediavault:~# systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d
           └─resolvconf.conf
   Active: inactive (dead)
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

That is a really hard question to answer. Sorry. I believe I followed this video: https://www.youtube.com/watch?v=NYJCq2FwRUo&t=744s

Then I updated via this video: https://www.youtube.com/watch?v=GjObhlFoUEU&t=1555s

Plugins:

• openmediavault-flashmemory 5.0.9
• openmediavault-omvextrasorg 5.6.6
• openmediavault-resetperms 5.0

As I mentioned, I changed the DNS Servers to 8.8.8.8. Is that not the same thing? How do I delete that file?

CG-NAT is carrier grade NAT. As IPv4 addresses are running out, his external IPv4 address is on a private network.

The problem is, his external address can not be reached by UDP (as it is behind NAT as seen from the "real" internet").

DNS uses UDP. so I am not sure if he can use the google DNS or has to take the one his provider offers.

try to start resolved:

sudo systemctl enable systemd-resolved.service

sudo systemctl start systemd-resolved.service

If this fails, remove resolvconf sudo apt-get remove resolvconf and try again.

Do not set a DNS in the UI and leave IPv4 on DHCP.

then try apt-get update to see if you can download some package info.

Zitat von Zoki

try to start resolved:

sudo systemctl enable systemd-resolved.service

sudo systemctl start systemd-resolved.service

If this fails, remove resolvconf sudo apt-get remove resolvconf and try again.

Do not set a DNS in the UI and leave IPv4 on DHCP.

then try apt-get update to see if you can download some package info.

Alles anzeigen

root@openmediavault:~# sudo systemctl enable systemd-resolved.service
Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service → /lib/systemd/system/systemd-resolved.service.
Created symlink /etc/systemd/system/multi-user.target.wants/systemd-resolved.service → /lib/systemd/system/systemd-resolved.service.

root@openmediavault:~# sudo systemctl start systemd-resolved.service
root@openmediavault:~#

Is that failure? Ha ha.

I also removed the DNS and am now getting updates in the list!

Perfect, try if it survives a reboot if not remove resolveconf and enable systemd-resolved again.

Started a new deployment in Portainer, just for kicks. And I think it worked!

Zitat von Zoki

Perfect, try if it survives a reboot if not remove resolveconf and enable systemd-resolved again.

Rebooting now...

Before that, I tried getting to Nextcloud and couldn't.

Survived the reboot.

And I have access to Nextcloud!

Now I need to set it up.

I know the DB password, but not totally sure about the rest. Do I need to add the port number after mariadb?

Yes, it is mariadb:5432

Zitat von Zoki

Yes, it is mariadb:5432

Got an error:

Error while trying to create admin user: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused

Would it not be mariadb:450? Nope. Didn't work either.

Zitat von atoddvr6

Now I need to set it up.

I know the DB password, but not totally sure about the rest. Do I need to add the port number after mariadb?

See macom guide and follow his instructions.

[How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose - Guides - openmediavault

You don't need to put the port, either use nextclouddb (the name of the service) or localhost.

Also, before clicking "Finish Setup" make sure you untick the small box that says to "Install default apps"

The guide has everything you need,

Nextcloud is up, my phone is connected and getting ready to back up. THANK YOU BOTH SO MUCH!!

Hi All,

I've installed nextcloud docker version on OMV.

I had to tinker with conf and ini file in order to be able to get the bigger file size for upload/download.

this was a while ago but I never thought of checking OMV webUI page.

as this is not my first setup, I knew from the very start to change the port to 82 for webUI.

I had a bit of power outage and found out that I can't access port 82.

I ran omv-firstaid and tried putting port 82 again for workbench, also tried port 85, but I'm not getting any luck.

Here's the output of it and wondering if anyone might be able to spot where the issue might be.

so in the docker containers, I've got nextcloud and nginx. Cheers all

----------

ID: prereq_nginx_certificates

Function: salt.state

Result: True

Comment: States ran successfully. Updating debian.

Started: 20:00:10.849222

Duration: 1776.825 ms

Changes:

debian:

----------

ID: remove_ssl_certificates_crt

Function: module.run

Result: True

Comment: file.find: []

Started: 20:00:11.136688

Duration: 12.469 ms

Changes:

----------

file.find:

----------

ID: remove_ssl_certificates_key

Function: module.run

Result: True

Comment: file.find: []

Started: 20:00:11.149495

Duration: 3.762 ms

Changes:

----------

file.find:

----------

ID: update_ssl_certificates

Function: cmd.run

Name: update-ca-certificates --fresh

Result: True

Comment: Command "update-ca-certificates --fresh" run

Started: 20:00:11.155242

Duration: 1463.566 ms

Changes:

----------

pid:

7629

retcode:

0

stderr:

stdout:

Clearing symlinks in /etc/ssl/certs...

done.

Updating certificates in /etc/ssl/certs...

129 added, 0 removed; done.

Running hooks in /etc/ca-certificates/update.d...

done.

----------

ID: remove_ssh_certificates

Function: module.run

Result: True

Comment: file.find: []

Started: 20:00:12.619122

Duration: 3.656 ms

Changes:

----------

file.find:

Summary for debian

------------

Succeeded: 4 (changed=4)

Failed: 0

------------

Total states run: 4

Total run time: 1.483 s

----------

ID: configure_nginx_site_webgui

Function: file.managed

Name: /etc/nginx/sites-available/openmediavault-webgui

Result: True

Comment: File /etc/nginx/sites-available/openmediavault-webgui is in the correct state

Started: 20:00:12.629479

Duration: 84.931 ms

Changes:

----------

ID: configure_nginx_security

Function: file.managed

Name: /etc/nginx/openmediavault-webgui.d/security.conf

Result: True

Comment: File /etc/nginx/openmediavault-webgui.d/security.conf is in the correct state

Started: 20:00:12.714639

Duration: 25.063 ms

Changes:

----------

ID: execute_nginx_ensite

Function: cmd.run

Name: nginx_ensite openmediavault-webgui

Result: True

Comment: Command "nginx_ensite openmediavault-webgui" run

Started: 20:00:12.741158

Duration: 14.782 ms

Changes:

----------

pid:

8957

retcode:

0

stderr:

stdout:

Site configuration file 'openmediavault-webgui' is already enabled.

----------

ID: prereq_nginx_service_monit

Function: salt.state

Result: True

Comment: States ran successfully. Updating debian.

Started: 20:00:12.756340

Duration: 851.798 ms

Changes:

debian:

----------

ID: configure_monit_collectd_service

Function: file.managed

Name: /etc/monit/conf.d/openmediavault-collectd.conf

Result: True

Comment: File /etc/monit/conf.d/openmediavault-collectd.conf is in the correct state

Started: 20:00:13.262359

Duration: 53.16 ms

Changes:

----------

ID: configure_monit_filesystem_service

Function: file.managed

Name: /etc/monit/conf.d/openmediavault-filesystem.conf

Result: True

Comment: File /etc/monit/conf.d/openmediavault-filesystem.conf is in the correct state

Started: 20:00:13.315712

Duration: 19.771 ms

Changes:

----------

ID: configure_monit_nginx_service

Function: file.managed

Name: /etc/monit/conf.d/openmediavault-nginx.conf

Result: True

Comment: File /etc/monit/conf.d/openmediavault-nginx.conf is in the correct state

Started: 20:00:13.335678

Duration: 16.943 ms

Changes:

----------

ID: configure_monit_omv-engined_service

Function: file.managed

Name: /etc/monit/conf.d/openmediavault-engined.conf

Result: True

Comment: File /etc/monit/conf.d/openmediavault-engined.conf is in the correct state

Started: 20:00:13.352821

Duration: 12.87 ms

Changes:

----------

ID: configure_monit_php-fpm_service

Function: file.managed

Name: /etc/monit/conf.d/openmediavault-phpfpm.conf

Result: True

Comment: File /etc/monit/conf.d/openmediavault-phpfpm.conf is in the correct state

Started: 20:00:13.365886

Duration: 13.489 ms

Changes:

----------

ID: configure_monit_rrdcached_service

Function: file.managed

Name: /etc/monit/conf.d/openmediavault-rrdcached.conf

Result: True

Comment: File /etc/monit/conf.d/openmediavault-rrdcached.conf is in the correct state

Started: 20:00:13.379566

Duration: 13.464 ms

Changes:

----------

ID: configure_monit_system_service

Function: file.managed

Name: /etc/monit/conf.d/openmediavault-system.conf

Result: True

Comment: File /etc/monit/conf.d/openmediavault-system.conf is in the correct state

Started: 20:00:13.393223

Duration: 25.788 ms

Changes:

----------

ID: configure_default_monit

Function: file.managed

Name: /etc/default/monit

Result: True

Comment: File /etc/default/monit is in the correct state

Started: 20:00:13.419201

Duration: 3.655 ms

Changes:

----------

ID: divert_default_monit

Function: omv_dpkg.divert_add

Name: /etc/default/monit

Result: True

Comment: Leaving 'local diversion of /etc/default/monit to /etc/default/monit.distrib'

Started: 20:00:13.423844

Duration: 20.259 ms

Changes:

----------

ID: configure_monit_monitrc

Function: file.managed

Name: /etc/monit/monitrc

Result: True

Comment: File /etc/monit/monitrc is in the correct state

Started: 20:00:13.444454

Duration: 27.514 ms

Changes:

----------

ID: divert_monit_monitrc

Function: omv_dpkg.divert_add

Name: /etc/monit/monitrc

Result: True

Comment: Leaving 'local diversion of /etc/monit/monitrc to /etc/monit/monitrc.distrib'

Started: 20:00:13.472164

Duration: 21.209 ms

Changes:

----------

ID: test_monit_config

Function: cmd.run

Name: monit -t

Result: True

Comment: Command "monit -t" run

Started: 20:00:13.495606

Duration: 18.496 ms

Changes:

----------

pid:

8964

retcode:

0

stderr:

stdout:

Control file syntax OK

----------

ID: reload_monit_service

Function: service.running

Name: monit

Result: True

Comment: The service monit is already running

Started: 20:00:13.547727

Duration: 58.108 ms

Changes:

Summary for debian

-------------

Succeeded: 13 (changed=1)

Failed: 0

-------------

Total states run: 13

Total run time: 304.726 ms

----------

ID: test_nginx_service_config

Function: cmd.run

Name: nginx -t

Result: True

Comment: Command "nginx -t" run

Started: 20:00:13.608401

Duration: 32.597 ms

Changes:

----------

pid:

8973

retcode:

0

stderr:

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: configuration file /etc/nginx/nginx.conf test is successful

stdout:

----------

ID: restart_nginx_service

Function: service.running

Name: nginx

Result: False

Comment: Job for nginx.service failed because the control process exited with error code.

See "systemctl status nginx.service" and "journalctl -xe" for details.

Started: 20:00:13.665101

Duration: 2766.158 ms

Changes:

----------

ID: monitor_nginx_service

Function: module.run

Result: False

Comment: One or more requisite failed: omv.deploy.nginx.default.restart_nginx_service

Started: 20:00:16.438169

Duration: 0.016 ms

Changes:

Summary for debian

------------

Succeeded: 6 (changed=4)

Failed: 2

------------

Total states run: 8

Total run time: 5.552 s

Thanks but yeah, I didn't make a backup of the file (silly me)

so I forgot the original numbers that I changed them from.

I will install similar setup on my other box, so that I can pull the default file across, but would you be able to point out which files in which directories should I be restoring? thanks