[Support] Fantucie App's


Recommended Posts

  • 2 weeks later...
  • 2 months later...
On 3/23/2023 at 4:48 AM, UnraidNet5bb25 said:

ERROR when try to get CA with DNS Chanllage

Command failed: . /opt/certbot/bin/activate && pip install certbot-dns-cloudflare==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') cloudflare && deactivate
[app         ] /bin/sh: .: line 0: can't open '/opt/certbot/bin/activate': No such file or directory

 

image.thumb.png.36fad553a0a0698c4450fbb8b512054c.png
image.thumb.png.ac05a86bd3b4e688627b0cc4be869337.png

Link to comment

I just installed Nginx-Proxy-Manager-Crowdsec

 

and I am getting this in the logs when adding/removing SSL certs:

 

[cert_cleanup] ----------------------------------------------------------
[cert_cleanup] Let's Encrypt certificates cleanup - 2023/06/01 22:44:04
[cert_cleanup] ----------------------------------------------------------
[cert_cleanup] 0 file(s) kept.
[cert_cleanup] 0 file(s) deleted.
[app         ] [6/1/2023] [10:44:04 PM] [Migrate  ] › ℹ  info      Current database version: none
[app         ] [6/1/2023] [10:44:04 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[app         ] [6/1/2023] [10:44:04 PM] [Setup    ] › ℹ  info      Logrotate completed.
[app         ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[app         ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[app         ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[app         ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[app         ] [6/1/2023] [10:44:04 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[app         ] [6/1/2023] [10:44:04 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[app         ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[app         ] [6/1/2023] [10:44:04 PM] [Global   ] › ℹ  info      Backend PID 451 listening on port 3000 ...
[supervisor  ] all services started.
[app         ] [6/1/2023] [10:44:05 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[app         ] [6/1/2023] [10:44:05 PM] [SSL      ] › ℹ  info      Renew Complete
[app         ] Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0
[app         ] [6/1/2023] [10:44:49 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf
[app         ] [6/1/2023] [10:44:49 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
[app         ]   "errno": -2,
[app         ]   "syscall": "unlink",
[app         ]   "code": "ENOENT",
[app         ]   "path": "/data/nginx/proxy_host/1.conf"
[app         ] }
[app         ] [6/1/2023] [10:44:49 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf
[app         ] [6/1/2023] [10:44:49 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
[app         ]   "errno": -2,
[app         ]   "syscall": "unlink",
[app         ]   "code": "ENOENT",
[app         ]   "path": "/data/nginx/proxy_host/1.conf"
[app         ] }
[app         ] [6/1/2023] [10:44:49 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf.err
[app         ] [6/1/2023] [10:44:49 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
[app         ]   "errno": -2,
[app         ]   "syscall": "unlink",
[app         ]   "code": "ENOENT",
[app         ]   "path": "/data/nginx/proxy_host/1.conf.err"
[app         ] }
[app         ] [6/1/2023] [10:44:49 PM] [Nginx    ] › ℹ  info      Reloading Nginx

 

I'm having numerous issues with this container.

 

The above logs pertain to me using my own cert given to me by Cloudfare.

 

I am not sure if it's a problem getting an error that it cannot delete those files.

Link to comment

Now onto the real issue. The one which is completely breaking my NginxProxyManager container. Remember this is a fresh installation.

 

I am trying to add this custom cert to NPM. I've done that successfully. You can see here in the logs:

 

[app         ] [6/1/2023] [10:55:43 PM] [SSL      ] › ℹ  info      Writing Custom Certificate: {
[app         ]   id: 3,
[app         ]   expires_on: '2038-04-01 15:40:00',
[app         ]   domain_names: [ '"CloudFlare,' ],
[app         ]   meta: {
[app         ]     certificate: '-----BEGIN CERTIFICATE-----\r\n' +
[app         ]       blah blah blah
[app         ]       '-----END CERTIFICATE-----',
[app         ]     certificate_key: '-----BEGIN RSA PRIVATE KEY-----\r\n' +
[app         ]       blah blah blah
[app         ]       '-----END RSA PRIVATE KEY-----'
[app         ]   },
[app         ]   modified_on: '2023-06-01 22:55:43',
[app         ]   created_on: '2023-06-01 22:55:43',
[app         ]   owner_user_id: 1,
[app         ]   provider: 'other',
[app         ]   nice_name: 'Cloudfare - xtu.icu'
[app         ] }
[app         ] Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0
[app         ] [6/1/2023] [10:56:02 PM] [Express  ] › ⚠  warning   Command failed: /usr/sbin/nginx -t 
[app         ] nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
[app         ] nginx: configuration file /etc/nginx/nginx.conf test failed
[app         ] [6/1/2023] [10:56:03 PM] [Express  ] › ⚠  warning   Command failed: /usr/sbin/nginx -t 
[app         ] nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
[app         ] nginx: configuration file /etc/nginx/nginx.conf test failed
[app         ] [6/1/2023] [10:56:05 PM] [Express  ] › ⚠  warning   Command failed: /usr/sbin/nginx -t 
[app         ] nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
[app         ] nginx: configuration file /etc/nginx/nginx.conf test failed

 

You can see the errors here in color:

image.thumb.png.5e93f0f049e7abbfff16b4a3a8b2f342.png

 

This causes my entire container to crash continuously. This happens specifically when I go to a site on my list in NPM and select to use the custom cert I just added.

 

I instead get those errors and this in the GUI: (excuse the blown out HDR screenshot)

 

image.png.d3c2dda9b3166daf401286d7fda3832e.png

 

I have no idea what is causing this at all...

 

Container is using just the normal settings... it seems the problem is that the certs are not being written to:

"/etc/letsencrypt/live/npm-2/fullchain.pem"

but I have no idea why... that's just my normal \\TOWER\appdata\NginxProxyManager-CrowdSec\letsencrypt folder... except for some reason it's completely empty???

 

This problem will allow me to start the container but it won't do anything and will just spam the logs with the errors in yellow.

Edited by plantsandbinary
Link to comment

I also just tried bypassing using Cloudfare's free SSL, and I tried to make a wildcard via NPM.

 

Instead I now got this error:

 

Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-6" --agree-tos --email "[email protected]" --domains "*.xtu.icu" --authenticator dns-cloudflare --dns-cloudflare-credentials "/etc/letsencrypt/credentials/credentials-6"
usage: 
  certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
it will attempt to use a webserver both for obtaining and installing the
certificate. 
certbot: error: unrecognized arguments: --dns-cloudflare-credentials /etc/letsencrypt/credentials/credentials-6

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

 

Looks like it's running the wrong command.

 

So it seems like this container isn't configured properly.

Link to comment

Hi. Try to install filerun ofi and get this

Unable to find image 'filerun/filerun:latest' locally
docker: Error response from daemon: manifest for filerun/filerun:latest not found: manifest unknown: manifest unknown.

Maybe somebody can help?

Link to comment
18 hours ago, plantsandbinary said:

I also just tried bypassing using Cloudfare's free SSL, and I tried to make a wildcard via NPM.

 

Instead I now got this error:

 

Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-6" --agree-tos --email "[email protected]" --domains "*.xtu.icu" --authenticator dns-cloudflare --dns-cloudflare-credentials "/etc/letsencrypt/credentials/credentials-6"
usage: 
  certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,
it will attempt to use a webserver both for obtaining and installing the
certificate. 
certbot: error: unrecognized arguments: --dns-cloudflare-credentials /etc/letsencrypt/credentials/credentials-6

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

 

Looks like it's running the wrong command.

 

So it seems like this container isn't configured properly.

Please check the wiki before ... https://wiki.unraid.kalifondation.fr/en/unraid/NginxProxyManager-CrowdSecimage.thumb.png.1aeea8fa3d1c135fef408f0bed21041f.png

Link to comment
4 hours ago, yarx said:

Hi. Try to install filerun ofi and get this

Unable to find image 'filerun/filerun:latest' locally
docker: Error response from daemon: manifest for filerun/filerun:latest not found: manifest unknown: manifest unknown.

Maybe somebody can help?

It same the docker image changed, I will update it right now, you can still use my template, but change the repo to that or wait for the update on the CA :) 
 

filerun/filerun:8.1

 

Link to comment

Also trying to install filerun-ofi and getting the error below on the logs. Container won't start. 

+ id -u user
+ echo 'The user user does not exist, creating...'
+ groupadd -f -g 1000 user
+ useradd -u 1000 -g user user
+ '[' '!' -e /var/www/html/index.php ']'
+ chown user:user /user-files
+ echo 'The next step is to download the latest FileRun installation zip from the FileRun client account and upload its contents inside the '\''html'\'' mounted folder.'
+ echo 'Then change ownership of the files like this:'
+ echo 'chown -R user:user /var/www/html'
+ echo 'Then open this server in your browser to complete the FileRun installation.'
+ exec /usr/bin/supervisord -c /filerun/supervisord.conf
Error: The directory named as part of the path /var/www/html/system/data/temp/supervisord.log does not exist
For help, use /usr/bin/supervisord -h
The user user does not exist, creating...
The next step is to download the latest FileRun installation zip from the FileRun client account and upload its contents inside the 'html' mounted folder.
Then change ownership of the files like this:
chown -R user:user /var/www/html
Then open this server in your browser to complete the FileRun installation.

 

Link to comment
On 6/5/2023 at 10:38 PM, learnin2walk said:

Also trying to install filerun-ofi and getting the error below on the logs. Container won't start. 

+ id -u user
+ echo 'The user user does not exist, creating...'
+ groupadd -f -g 1000 user
+ useradd -u 1000 -g user user
+ '[' '!' -e /var/www/html/index.php ']'
+ chown user:user /user-files
+ echo 'The next step is to download the latest FileRun installation zip from the FileRun client account and upload its contents inside the '\''html'\'' mounted folder.'
+ echo 'Then change ownership of the files like this:'
+ echo 'chown -R user:user /var/www/html'
+ echo 'Then open this server in your browser to complete the FileRun installation.'
+ exec /usr/bin/supervisord -c /filerun/supervisord.conf
Error: The directory named as part of the path /var/www/html/system/data/temp/supervisord.log does not exist
For help, use /usr/bin/supervisord -h
The user user does not exist, creating...
The next step is to download the latest FileRun installation zip from the FileRun client account and upload its contents inside the 'html' mounted folder.
Then change ownership of the files like this:
chown -R user:user /var/www/html
Then open this server in your browser to complete the FileRun installation.

 

In the mounted path can you see filerun file ? 
If yes then chmod the path permission to 777 then re run the container if no, please re message me and I will check on my side in the test server because for now I have no problem in the latest 

Link to comment
On 6/8/2023 at 8:59 AM, Fantucie said:

In the mounted path can you see filerun file ? 
If yes then chmod the path permission to 777 then re run the container if no, please re message me and I will check on my side in the test server because for now I have no problem in the latest 

I have the same problem, directories are created but chmod doesnt fix the issue. Directories are empty.

The container is up for only a few seconds before it dies with that same error. 

Edited by lordvaderxiii
Link to comment
3 hours ago, lordvaderxiii said:

I have the same problem, directories are created but chmod doesnt fix the issue. Directories are empty.

The container is up for only a few seconds before it dies with that same error. 

image.png.bc45425e4a401fd4176ad5e44293ef93.png
FileRun has stopped every free plans, and it same you canno't download it and even if you could, you wouldn't be able to use it without paying an license

  • Confused 2
Link to comment
  • 1 month later...

I had trouble viewing the GUI for the vnStat container. Defaults were left in the template during install except Network Type. I had set that to my custom network.

 

The problem after first install was that clicking the WebUI link in Unraid would bring up a blank page using Chrome on my PC. This was the only machine/browser I tried. The URL listed was something link blocked/blank. Sorry. I did not capture the exact detail. This behaved differently from other containers. I tested using my machine's local IP and the container port. That too was not successful.

 

I added this to the container and was able to reach the GUI. Click  Add another Path, Port, Variable, Label or Device and set the port details.

Config Type: Port
Name: Host Port for 8685
Container Port: 8685
Host Port: 8685
Default Value: 8685
Connection Type: TCP

 

Once that was done it worked for me.

 

Note that I had changed one other container before this success. I adjusted the WebUI setting (under advanced view). The default was "http://[IP]:8685/". I changed it to "http://[IP]:[PORT:8685]" to match other functioning containers on my system. I'm not sure if that had any bearing on getting the GUI to show.

 

One last change was it had an inactive interface as far as I can tell. So after issuing these commands, my only active interface, eth0, was left. The two command issued start with vnstat.

 

/ # vnstat --iflist
Available interfaces: tunl0 eth0 (10000 Mbit) 
/ # vnstat -i tunl0 --remove --force
Interface "tunl0" removed from database.
The interface will no longer be monitored. Use --add if monitoring the interface is again needed.
/ # 

 

Hope this helps others.

Link to comment
  • 2 weeks later...
On 7/13/2023 at 3:02 PM, Bait Fish said:

I had trouble viewing the GUI for the vnStat container. Defaults were left in the template during install except Network Type. I had set that to my custom network.

 

The problem after first install was that clicking the WebUI link in Unraid would bring up a blank page using Chrome on my PC. This was the only machine/browser I tried. The URL listed was something link blocked/blank. Sorry. I did not capture the exact detail. This behaved differently from other containers. I tested using my machine's local IP and the container port. That too was not successful.

 

I added this to the container and was able to reach the GUI. Click  Add another Path, Port, Variable, Label or Device and set the port details.

Config Type: Port
Name: Host Port for 8685
Container Port: 8685
Host Port: 8685
Default Value: 8685
Connection Type: TCP

 

Once that was done it worked for me.

 

Note that I had changed one other container before this success. I adjusted the WebUI setting (under advanced view). The default was "http://[IP]:8685/". I changed it to "http://[IP]:[PORT:8685]" to match other functioning containers on my system. I'm not sure if that had any bearing on getting the GUI to show.

 

One last change was it had an inactive interface as far as I can tell. So after issuing these commands, my only active interface, eth0, was left. The two command issued start with vnstat.

 

/ # vnstat --iflist
Available interfaces: tunl0 eth0 (10000 Mbit) 
/ # vnstat -i tunl0 --remove --force
Interface "tunl0" removed from database.
The interface will no longer be monitored. Use --add if monitoring the interface is again needed.
/ # 

 

Hope this helps others.


Hello there ! 
I just seen your message sorry for the *very very* late answern yeah the port [PORT:8685] was missing on the template, I just fixed it thanks for your message, new user shouldn't have to fix it now 😃

For the commands ect, you should take a look toward my wiki about VnStat everything is *normally* aleadry said on it !
https://wiki.unraid.kalifondation.fr/en/unraid/VnStat & https://wiki.unraid.kalifondation.fr/fr/unraid/VnStat

Link to comment
  • 4 weeks later...

Hello,

 

I use your Seafile docker for four months :

1676395899_Capturedecran2023-08-16a19_23_12.png.91dd9dd1d29fc97938b3033391a02933.png

917017829_Capturedecran2023-08-16a19_23_52.thumb.png.f10a6423022277e05dd7a8426a56b7fd.png

 

I love it. Thanks !

 

Right now, i use "Backup/Restore Appdata" to make a backup of the container, which require to stop Seafile.

As i am the only user and store small amount of data, it took less than 10min, which i do overnight :

925676483_Capturedecran2023-08-16a19_25_37.png.790f68e9ba4af4c97df3ef713995c254.png

 

69026461_Capturedecran2023-08-16a19_32_10.png.11f6a0c7753ae9a1dcf175bbf4a51caf.png

 

I think it is time to move forward.

I would like to store more data, and also open it to my family, mainly to store photos/videos of my nephews, as no one in the family really understand the word "MAKE BACKUPS" or "A file in one place is a dead file".

 

So, the total amount of data will grow, and i think stopping the container and make an archive of 1 Tb+ won't be a right solution.

 

What is recommandation ?

 

To give you some context :

- appdata (and seafile container) is on a zfs pool :

608873514_Capturedecran2023-08-16a19_36_53.thumb.png.ce68a7bcbcc0be6ad74976179a4615cf.png

 

- I kept my Appdata backup on the array inside /mnt/disk5/Backup/UNRAID/appdata

 

- Every day, a second UNRAID server is turn on and use this script to backup the main server :

On the backup server, inside a array, i have a zfs disk waiting for some snapshots :

1955125425_Capturedecran2023-08-16a19_40_02.thumb.png.d5c592fd6e5f106fd9ca22d1f3bcb1d5.png

 

I think i can manage something with that, but i don't know if zfs snapshot or rsync is a good solution, as Seafile data can be updated at any time.

 

Thanks you for your time, and for the container !

 

K.

Link to comment
  • 1 month later...
  • 3 weeks later...

NginxProxyManager-CrowdSec: I am having problems renewing the SSL certs. It always says "Internal Error".

 

I read your Wiki: "When creating SSL, using the button "Use a DNS challenge" does not work ..." But I am not using this button.

 

Port 80 and 443 are also forwarded correctly. Back in August I was able to create the certificates. Now, renewing or creation always fails.

Link to comment
  • 3 weeks later...
On 10/18/2023 at 11:35 AM, el_fredo said:

NginxProxyManager-CrowdSec: I am having problems renewing the SSL certs. It always says "Internal Error".

 

I read your Wiki: "When creating SSL, using the button "Use a DNS challenge" does not work ..." But I am not using this button.

 

Port 80 and 443 are also forwarded correctly. Back in August I was able to create the certificates. Now, renewing or creation always fails.

Hello sorry for the very late answer, I've been quite busy irl, I would like to see your log on container side when this error appear to see what concretly is the error if you still have it, feel free to join the discord there is more poeple to help and less latency for answer, I sadly don't have full time to check up here always unless than on discord ^^' 

Link to comment
  • 3 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.