commenting out [::]:80 and [::]:443 on the nginx.config of the Container also no solution that works
Beiträge von fraxor
-
-
Hi guys,
i'm quite frustrated... my reverseproxy which i use the docker container from Linuxserver.io (letsencrypt) fails...
when i look to the logs on the container i see following output:Codenginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Since i've posted already to the LinuxServer.io forum they suggested to have a look to my Host IPv6 Settings.Now can some one help me figure out where this Line 2 Error comes from?
have please a look to my troubleshooting done so far:
Code$ sudo nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful
Code
Alles anzeigen$ systemctl status nginx.service ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-01-13 22:47:45 CET; 14min ago Docs: man:nginx(8) Process: 4146 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=0/SUCCESS) Process: 4152 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Process: 4148 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Main PID: 4153 (nginx) Tasks: 5 (limit: 4915) Memory: 6.1M CPU: 183ms CGroup: /system.slice/nginx.service ├─4153 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; ├─4154 nginx: worker process ├─4155 nginx: worker process ├─4156 nginx: worker process └─4157 nginx: worker process
Code$ systemctl status networking.service ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2020-01-13 23:20:30 CET; 29s ago Docs: man:interfaces(5) Process: 916 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Process: 876 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/S UCCESS) Main PID: 916 (code=exited, status=1/FAILURE) CPU: 186ms
Code
Alles anzeigen$ cat /etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback # wlp4s0 network interface auto wlp4s0 allow-hotplug wlp4s0 iface wlp4s0 inet dhcp dns-search home iface wlp4s0 inet6 manual pre-down ip -6 addr flush dev $IFACE # Include additional interface stanzas. source interfaces.d
Code$ nmcli connection show NAME UUID TYPE DEVICE SSID-Name 50fc36a6-2238-41d5-8b82-6c2553a9dfcb 802-11-wireless wlp4s0 br-64a2b133a52b dbf2622b-ff7d-4ed2-8f1d-645ef91b7786 bridge br-64a2b133a52b br-b5c7fdf5f721 3442981b-62fa-41ec-af1b-112e876e9281 bridge br-b5c7fdf5f721 br-fc20d2948ce4 2f34fc6f-8164-44ab-9eef-cdb92346a9aa bridge br-fc20d2948ce4 docker0 a41b4380-f06e-4c25-b4f9-6b46f2acb858 bridge docker0 Ifupdown (wlp4s0) 571967bf-b10a-641e-b7fb-c9d62b54b91a 802-3-ethernet -- Wired connection 1 b14e8508-b8c7-3de3-b33c-f5af70c19767 802-3-ethernet --
Thanks for the help and regards!
etfraxor -
Hi guys, just wantet to mention that i found the error!
Docker-Container of Gitea was the issuer...
now i moved to Gogs and hope it will work.
was not able to figure out where the problem was... Logs was not logged so no chance to find out how to solve the problem.
if i have problem with Gogs also, then i have to check the reverseproxy conf of letsencrypt, because those are identical.i will close when i have solved the problem
Thanks for the Help @Adoby
Cheers
-
fraxor: if your document storing solution is able to access SMB or FTP storage then all should be fine for you - welcome and I would appreciate feedback when you have one in place!
I have Nextcloud running and works excellent!
but for my mobile device i wanted to edit the files, and with the Nextcloud app it is not possible, as far as i know.
but i will definitely give it a try and give you feedback -
Why don't buy an onboard CPU?
I have considerate this in my build (j5005). but at the end for the same costs, i went with an AMD Ryzen 3 1200 combined with a
ASUS Prime B450M-A. So i'm able now to stream 4k without a problem and in future i can still upgrade my CPU if needed.
Power consumption should be quite low as well. -
This was the hard part for me - trying to figure out which of my installed plugins came as core plugins from OMV and which ones came from OMV extras. Rather than try to figure that out I just made a list of all installed plugins, removed them all, and then installed whichever ones on my list that I could find for OMV 5. I'm pretty sure I got them all back except for the DockerGUI plugin. Portainer from OMV extras 5 filled that need.
As for which ones you have installed, look in the Plugins list - the ones with the green dot are installed.
I would make this the same way...
all the one with the green dot in the plugins.
also as i'm confident not using the docker gui, i dont care to uninstall completely the omv extras.thanks for specify the workflow of upgrade from omv4 to 5.
i need to make an clonezilla (because with dd i could not restore a backup successfully due of running container when dd the whole disk).
-
This is the procedure I used. It worked for me, but you should never try anything like this unless you have a known good verified to be restorable backup of your OMV 4.
Codehttps://forum.openmediavault.org/index.php/Thread/27909-ETA-for-OMV-5-0-weeks-months-quarters-2020/?postID=219830#post219830
A few notes. You should make a list of all your plugins and verify which of them are also available for for OMV 5. See:
Any OMV 4 plugin that has been ported to OMV 5 can be left installed on OMV 4. If there isn't one ported to OMV 5 then you must uninstall the plugin and seek an alternate method to have the same capability - usually provided by a docker. I didn't take any chances with this. I made a list of all my installed plugins on OMV 4, then I removed them all, did the upgrade, and then installed all the plugins again using those available for OMV 5.
Good luck!
Thank you @gderf for the Links, i'll give it a shot when i get some time next year
and then i have to ask you how ti find out the installed Plugin, because i see some Plugins in OMV (which those are not mentioned in the binary.com link) some in OMV-Extras.
-
OMV5 is ready to go but still needs some more testing. In the meanwhile OMV6 development has started.
Nice to know!
is a way to upgrade form ovm 4.x to 5.x?
what are the skillset to contribute developing the OMV? -
@Adboy
i will give it a shot and post my result.
probably will take me several days... as i sed it happens randomly (i will run every step for min 24h - 48h).thank you very much for this approach... hope will narrow down the issuer.
cheers
-
Well Done!
is exactly what i wanted to build but with 4 2.5'' HDD.
unfortunately i need way more then 4GB RAM and for the OnlyOffice DocumentServer is not for ARM yet...
maybe in the future i will make such a box for backup or retropi.Thanks for Sharing this project with us and also the 3D Files
-
Hi Community, i could need some help in troubleshoot a problem of mine...
since i have a new server, the server is keeping disconnecting it or go randomly crazy...Specs of the server:
Processor: AMD Ryzen 3 1200
Motherboard: ASUS Prime B450M-A
RAM: Corsair Vengeance LPX (2x, 16GB, DDR4-2400, DIMM 288)
120GB SSD
Raid 5 with 4x2TB and a single 1TB HDDnow to the problem...
how can i trhoubleshoot the moment and the cause of the Network failure?here i have some Picture from today:
https://ibb.co/PCGzrZg
https://ibb.co/QHvRSZq
https://ibb.co/095CmRZ
https://ibb.co/YLdD8Xz
https://ibb.co/FnGzd0yI have running following Container:
- Linuxserver/letsencrypt
- gitea
- nextcloud
- mariadb
- pihole
- plex
- transmission
- onlyoffice
- duckdnsi do running following Services:
- FTP
- ClamAV
- Apple Filing
- SSHi can provide the syslogs or the system report.
any help is really appretierte, because it's really annoying if i relay on my nextcloud and git and it goes randomly down.
-
Sounds like you could write a style package for OMV5. But dont know if its worth the effort.
No, Probabely not... i think the OMV-Team changed backend Technology and is absolutely not with the effort... beter waiting for OMV 5 go in Production
-
Oh sorry, for my stupid questions.
The solution is at openmediavault.org -> latest news
I didn´t have had a look before my questions.
yeah... latest Blog Post
-
Hi OMV-Team and Comunity
the new GUI looks hot!!!
good work!it will be possible to implement this with the OMV 4?
-
Morlan,
you know what?! i could solve it...
I created a new Subdomain on DuckDNS and this made the trick...everything was the same...
maybe with the change of my machine and stuff... the certificate or something else broke.well... now I'm happy again!
Thanks for your time!
-
Hi Morlan,
thx for your hint.
normally on my way when I execute the docker-compose up -d then this will create the network lets encrypt_proxyWhen I inspect the docker network, then letsencrypt and nextcloud container are on the same network.
I think that the problem is on the letsencrypt container. Because by don't activate the reverse proxy-conf on the nginx, and don't make the modification on the config.php of nextcloud, Nextcloud is working with the URL: https://192.168.1.x:445
-
i would use the rsync method:
sudo rsync -aAXv /dev/sda1 /dev/sdb1
Make sure to edit the sda1 and sdb1 acording to your sdd's.
cou can check this via lsblk
-
Hi Forum,
i had this setup 2 weeks ago up and running. Since i had a HW failure, i needed a new MainBoard, CPU and RAM.
Now to my problem... i cant reach to my Nextcloud, Bitwarden and GiTea over the internet via https.
All the Containers come up without problem. Logs shows no error...
I deleted all the Containers and the volumes to see if i can solve the error but nothing.i'm desperate searching the error since 1 week allredy...
DuckDNS
Code: docker-compose.ymlversion: "2" services: duckdns: image: linuxserver/duckdns container_name: duckdns env_file: - ./duckdns.env volumes: - /var/docker/appdata/duckdns/:/config restart: unless-stopped
Code: duckdns.envPUID=1001 PGID=100 TZ=Europe/Zurich SUBDOMAINS=mysubdomain TOKEN=TOKEN_FROM_DNS_SERVICE_PROVIDER
LetsencryptCode: docker-compose.yml
Alles anzeigenversion: "2" services: letsencrypt: image: linuxserver/letsencrypt container_name: letsencrypt cap_add: - NET_ADMIN env_file: - ./letsencrypt.env volumes: - /var/docker/appdata/letsencrypt/:/config depends_on: - duckdns networks: - proxy ports: - 444:443 restart: unless-stopped networks: proxy:
Code: letsencrypt.envPUID=1001 PGID=100 TZ=Europe/Zurich URL=mysubdomain.duckdns.org SUBDOMAINS=wildcard VALIDATION=duckdns DUCKDNSTOKEN=TOKEN_FROM_DNS_SERVICE_PROVIDER EMAIL=EMAIL@EMAIL.COM
NextCloud
Code: docker-compose.yml
Alles anzeigenversion: "2" services: nextcloud: image: linuxserver/nextcloud container_name: nextcloud environment: - PUID=1001 - PGID=100 - TZ=Europe/Zurich volumes: - /var/docker/appdata/nextcloud/config:/config - /sharedfolders/nextcloud/:/data ports: - 445:443 - 82:80 restart: unless-stopped networks: default: external: name: letsencrypt_proxy
I did also the Modification on the Letsencrypt-ReverseProxy-Conf and on the Nextcloud Conig.php
looks like this:PHP
Alles anzeigen<?php $CONFIG = array ( 'trusted_domains' => array ( 0 => '192.168.1.130:445', 1 => 'nextcloud.mysubdomain.duckdns.org', ), 'trusted_proxies' => ['letsencrypt'], 'overwrite.cli.url' => 'https://nextcloud.mysubdomain.duckdns.org/', 'overwritehost' => 'nextcloud.mysubdomain.duckdns.org', 'overwriteprotocol' => 'https', ... );
Code: nextcloud.subdomain.conf
Alles anzeigenserver { listen 443 ssl; listen [::]:443 ssl; server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nextcloud nextcloud; proxy_max_temp_file_size 2048m; proxy_pass https://$upstream_nextcloud:443; } }
many Thanks for the help!Regards
etfraxor -
Hi @topi
did you manage to get the full text search for NextCloud with the ElasticSearch Container to work? I'm also starting this project, but don't know where to start.
here is a guide in German, but is not made with Container solution.thanks for replay if you managed to run it.
-
Probably this is the wrong place to ask. You should visit the forum (or similar) of gitea.
Thanks for replaying macom!
i was not able to bring it to work in any way.
i have purged all gitea and reinstalled. On the GUI installation i was able to set it like i wanted to and now works just fine.hope some one can profit from this answer.
peace out