Beiträge von Ruschi

hi guys..

I get an error after updating/upgrading..

Can U please have a look at it:

Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete sind zurückgehalten worden:
openmediavault
Die folgenden Pakete werden aktualisiert (Upgrade):
emby-server login passwd
3 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
2 nicht vollständig installiert oder entfernt.
Es müssen noch 0 B von 12,0 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 968 kB Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n] j
(Lese Datenbank ... 85918 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../login_1%3a4.2-3+deb8u3_amd64.deb ...
Entpacken von login (1:4.2-3+deb8u3) über (1:4.2-3+deb8u1) ...
Trigger für man-db (2.7.0.2-5) werden verarbeitet ...
login (1:4.2-3+deb8u3) wird eingerichtet ...
(Lese Datenbank ... 85918 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../passwd_1%3a4.2-3+deb8u3_amd64.deb ...
Entpacken von passwd (1:4.2-3+deb8u3) über (1:4.2-3+deb8u1) ...
Trigger für man-db (2.7.0.2-5) werden verarbeitet ...
passwd (1:4.2-3+deb8u3) wird eingerichtet ...
(Lese Datenbank ... 85918 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../emby-server_3.2.3-18.1_all.deb ...
Stopping Emby Server!
Entpacken von emby-server (3.2.3-18.1) über (3.2.1-17.1) ...
Trigger für systemd (215-17+deb8u6) werden verarbeitet ...
nginx-full (1.10.2-4~bpo8+1) wird eingerichtet ...
Job for nginx.service failed. See 'systemctl status nginx.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript nginx, action "start" failed.
dpkg: Fehler beim Bearbeiten des Paketes nginx-full (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von nginx:
nginx hängt ab von nginx-full (<< 1.10.2-4~bpo8+1.1~) | nginx-light (<< 1.10.2-4~bpo8+1.1~) | nginx-extras (<< 1.10.2-4~bpo8+1.1~); aber:
Paket nginx-full ist noch nicht konfiguriert.
Paket nginx-light ist nicht installiert.
Paket nginx-extras ist nicht installiert.
nginx hängt ab von nginx-full (>= 1.10.2-4~bpo8+1) | nginx-light (>= 1.10.2-4~bpo8+1) | nginx-extras (>= 1.10.2-4~bpo8+1); aber:
Paket nginx-full ist noch nicht konfiguriert.
Paket nginx-light ist nicht installiert.
Paket nginx-extras ist nicht installiert.

dpkg: Fehler beim Bearbeiten des Paketes nginx (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
emby-server (3.2.3-18.1) wird eingerichtet ...
Fehler traten auf beim Bearbeiten von:
nginx-full
nginx
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@NAS:~# service nginx restart
Job for nginx.service failed. See 'systemctl status nginx.service' and 'journalctl -xn' for details.

command:

systemctl status nginx.service

● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
Active: failed (Result: exit-code) since Sa 2017-02-25 07:25:41 CET; 46s ago
Docs: man:nginx(8)
Process: 8574 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)

Feb 25 07:25:41 NAS nginx[8574]: nginx: [emerg] invalid number of arguments...18
Feb 25 07:25:41 NAS nginx[8574]: nginx: configuration file /etc/nginx/nginx...ed
Feb 25 07:25:41 NAS systemd[1]: nginx.service: control process exited, code...=1
Feb 25 07:25:41 NAS systemd[1]: Failed to start A high performance web serv...r.
Feb 25 07:25:41 NAS systemd[1]: Unit nginx.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

Hey guys.. I still work on this problem and I still have no solution..

In sites-enabled I have the openmediavault-webgui.conf (for sure) and the zzz-omv.conf for Letsencrypt.
so everything goes to https://

I´m still not be able to have access to my TVserver which runs on port 9981.
I always get an 404 error..

It drives me crazy..

Und? Ich konnte mich zeitlich noch nicht mit beschäftigen..

Hat das schon jemand umgesetzt.. ?

Ich habe mir jetzt nochmal die nginx-config besonders den teil der "sites-enabled" angesehen.
dort gibt es also die openmediavault-webgui.conf und die zzz-omv-nginx.conf (für nextcloud) in meinem Fall.

Ich könnte nun also z.B die webgui.conf um einen server_block erweitern?!

location ^~ /tvserver {
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://127.0.0.1:9981;
proxy_redirect off;
}

update: but still on the old HDD..

I did following steps. everything running on ubuntu LIVE system.

-shrinked my Partition on HDD to fit the SSD using gparted.
-created new ext4 partition on my SSD.
-rsync both drives.
-copied the new UUID in /etc/fstab
-grub2 update

If I boot from my SSD now, I still get the error "cannot get C/S/H values".

I googled the C/S/H error but I still don´t find a solution for it.
Are there other ways to get my data from the old HDD?

So I should be able to try a New Installation On my SSD and then i can copy back my old files within my config? I used pooling with mergerfs and so on.

I tried this but i ran in errors.. I shrinked the partition but if i try to Boot from the old HDD now i get "cannot get C/H/S vallues"
Lucky that I made an image with dd .. I hope I can copy it back. I also made a backup with the OMV backup tool. How could be a scenario if I Start a New Installation with my SSD. Can I then copy everything back to my SSD?!

Zitat von Ruschi

will this be correct :

{
listen 80;
listen [::]:80;
location /tvheadend {
return 301 https://$host:9981/;
}
}

Alles anzeigen

i tested this. didn´t work

I created a new document which is tvheadend.conf in /etc/nginx/openmediavault-webgui.d/

if I use the lines with port 80 i get an error by nginx that listening twice on port 80 isn´t okay.
If I only use

location /tvheadend {
return 301 https://$host:9981/;
}

I get error: net:ERR_Connection_Closed (the website couldn´t be loaded)

Es läuft mittlerweile alles. Außer das aufrufen von services via domain/service.

will this be correct :

{
listen 80;
listen [::]:80;
location /tvheadend {
return 301 https://$host:9981/;
}
}

hello.

can someone explain how to proxy_pass to https://mydomain/nextcloud instead of the nextcloud-port?
I use nginx and letsencrypt

Zitat von luxflow

• first install omv-nginx
• add entry and see attachments (this is only for tvheadend and just example but it is similar to others but should always check application specific proxy pass configuration)
• omv schdule job -> select letsencrypt jobs -> run (this step is not required if you don't use sub domain that is something like tv.yourdomain.com)

ty very much..

It works but I get an 404 error.. but i read that this is more a "problem" of Tvheadend. I have to read more.
I also did a SSL test yesterday .. looks good but the key exchange is weak. I should use the diffie-hellman params.

Zitat von luxflow

googling following keyword

tvserver nginx reverse proxy
couchpotato nginx reverse proxy
nextcloud nginx reverse proxy

give you application specific reverse proxy configuration

if you use same domain, only different thing is path (/tvserver /couchpotato /nextcloud)
you just get only one cert from LE for that domain

Alles anzeigen

In which .conf do I now have to put in the proxy_pass configuration?
what about this folder /.well-known/acme-challange/

My proxy_pass looks like this.

#tvheadend
server {
listen [::]:80;
server_name nas.xxxxxx.com 192.168.178.20;
location /tvheadend {
proxy_set_header HOST $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://127.0.0.1:9981;
}
}

Zitat von luxflow

Code

#completely remove old letsencrypt
apt-get purge openmediavault-letsencrypt
#remove letsencrypt directory
rm -rf /etc/letsencrypt
#reinstall
apt-get install openmediavault-letsencrypt

@Ruschi
First remove le cronjob in OMV, and try this script to completely remove omv-letsencrypt and reinstall
After that try generate letsencrypt cert again

"Because I'm happy"

this worked.
Now I can choose it. Great..

I generated a New certificate in LE but i get errors. Certificate is okay but if i choose it in the Main settings i got this error. Regenerating tells certificate is okay. hint: I use backports kernel...

Ich habe verstanden das eigentlich "nur" die sites_enabled "erweitert" werden muss. Thema proxy_pass. Beispiele liefert ja dein post im RPi forum. Ich muss eh von vorne anfangen. Nextxloud läuft bei mir, allerdings nicht mit Letsencryt und SSL. Und auch alles nicht so konform.
Ich kann mich erst in paar Tage damit auseinandersetzen..

1st post point 5 in this thread says the LE cert can be chosen in General SSL section. And this is my Problem. There is no LE cert to choose. I can only choose my self generated cert.

Zitat von luxflow

I cannot understand your problem
Please describe more detail what is your issue and what you did also what you want

You don't need choose LE in nginx manually (I'm not sure what you mean choose LE in nginx)
omv-letsencrypt do all things automatically you don't need to manually edit nginx configuration

enable `Schedule Refresh` -> put your domain in `Domain`, email in `Email`, '/var/www/openmediavault/' in `WebRoot` -> save & generate certificate

Okay.. Then everything is like it should. Ty very much.. !!

Zitat von luxflow

Don't need to delete old cert

The Problem is: I cant choose LE in nginx AS example

Hi guys.. I created a SSL cert some month ago but now i want to use LE. How can i delete the "old" one?!

I have a question .

I installed LE succesfully on my maschine.
now i want to have access to different ports/services on my server over the internet. but always on the same domain !!. for example: domain/tvserver-- domain/couchpotato-- domain/nextcloud etc.

i read a tutorial using nginx proxy_pass function but i´m too dumb to get it to work.

maybe someone can help an old guy..