mattie112

Members
  • Content Count

    198
  • Joined

  • Last visited

Community Reputation

23 Good

1 Follower

About mattie112

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It will be (see "Cron jobs in Docker" on that page) docker exec --user www-data <container> /usr/local/bin/php /var/www/html/artisan firefly-iii:cron Just confirm the name of the container in your Unraid
  2. It needs to be added to the proxy module config (http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffering) Afaik that can be simply added to the "custom nginx configuration" in NPM I would suggest to simply try it... And if it doesn't work you can try to manually edit the file in /mnt/user/appdata/NginxProxyManager/nginx/proxy_host
  3. You can use the User Scripts plugin and then add the comments to run there. For example I run my nextcloud cron every 5 minutes with this as script docker exec -u www-data Nextcloud php -f /var/www/html/cron.php So you docker exec (then optionally the user) then the name of the container and last the command you want to run
  4. I'm sorry what I said is not 100% correct. You can use 80/443 but then you MUST use "br0" as network. As your unraid already listens to 80 (and/or 443). By using "br0" your NPM get it's own IP. You really only need my fork if you use IPv6 as you cannot simply forward a port there (and then the solution is to run NPM om 80/443). If you use IPv4 only then yes use br0 and have the config the way you have it.
  5. If you want your NPM to be on 80/443 you'll need to use my fork (or change it yourself): as the current image does not support it (yet). What container are you using for nextcloud? The official container (https://hub.docker.com/_/nextcloud) uses http and suggest you use a reverse-proxy (like NPM) to terminate SSL edit: So that would be 80 -> 8888 for example in your nextcloud docker config and then http://unraidip:8888 in NPM
  6. Yeah that seems to fix it! I've noticed some routes where added: The 'shim-br0' ones didn't exist earlier
  7. It should work but I'm assuming you don't have a valid SSL certificate on your nextcloud internal endpoint so I think it will fail somewhere due to that. Nextcloud works fine with http, see my screenshot, I only forward 80 of the nextcloud container to 8888 and use that in NPM
  8. Due to a power outage my server did a hard reboot and now I have issues with my reverse proxy. It seems it cannot access any containers listening on the IP of the host. Host network access is enabled. Any ideas? 192.168.100.200 is my Unraid IP root@Tower:~# docker exec -it NginxProxyManager bash bash-5.0# ping 192.168.100.200 PING 192.168.100.200 (192.168.100.200): 56 data bytes ^C --- 192.168.100.200 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss bash-5.0# ping 192.168.100.220 PING 192.168.100.220 (192.168.100.220): 56 data bytes 64 byte
  9. Normally the flow is: http endpoint locally (eg http://1.2.3.4:port) https endpoint 'exposed' (eg https://domain.com) In this case the application itself (nextcloud) does not need to know anything from SSL, not the cipers not the certificate, nothing. NPM simply accepts the incoming request, handles the SSL part and then forwards the traffic to a local (unencrypted) endpoint. You are doing: https external -> https internal In that case you would need to have a SSL cert on both endpoints For example:
  10. I've noticed a problem related to the changes I've made regarding saving the config file. Last night my server went down due to a lightning strike killing the power. And I've notices it remained offline on my monitoring. So: I checked the config but hey there are no "snmp" settings anymore how strange. Went to reinstall/download the plugin and then I saw: Executing install script for unraid-snmp-2021.05.21-x86_64-1.txz. Set permissions and move into dir /usr/local/emhttp/plugins/snmp Set shell script executable permissions Set read only permissions for other files Checking if /etc/r
  11. Are you sure you want to proxy traffic TO a HTTPS endpoint? Normally your 'internal' endpoint is unencrypted/http.
  12. So you have a proxy configured in NPM for your nextcloud? On myurl.com? And http://myurl.com works but https://myurl.com does not? If it is configured it should work (but with a default/invalid certificate). Is there anything in the logs of NPM why the certificate fails?
  13. Great thanks I will try that! Probably had that set when testing unraid (as this is a case I've tested) but now it was set to 0 indeed.
  14. I have been using Unraid for about a year now and today I have been sorting/moving some stuff. At some point my cache drive was full. Not a problem right? It should go to the array? But it does not seem to work, I thought it would automatically do that but perhaps I'm wrong and a full cache drive simply has never happend yet. My cache pool: (I cancelled the file transfer so I guess ~10gb will be removed soon) The share I am writing to: "Yes indicates that all new files and subdirectories should be written to the Cache disk/pool,
  15. For the people using my fork, (the port 80/443 one): I have just merged the latest v1.16.1 into my branch and pushed a new version. I'm doing this manually so I don't really push every version (as I have to notice it). But if there is any major issue of a fix that you'd like just send me a message and I will push it