Dark-Raptor
-
Posts
13 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Dark-Raptor
-
-
i had the same error it seems when i was on version 1.7.1 or somthing i made a change to one of my proxys and that seems to have added extra data into my config file
listen 8080;
listen [::]:80;this was causing the container not to work
i just did a notepad++ search in "NginxProxyManager\nginx\proxy_host" for "[::]:80" and it found it in 4.conf
after commenting the line out "#listen [::]:80;" the container then loaded with that host being unknown status then i just resaved and it corrected the file and add httpslisten 8080;
#listen [::]:80;listen 4443 ssl http2;
#listen [::]:443;with this change and adding "DISABLE_IPV6 true" i was able to get things working again
-
that seemed to work thanks
9 hours ago, dlandon said:Working fine for me. Remove the /flash/config/plugins/file.activity/ folder and try again.
-
currently having a problem installing this plugin im getting the error
unraid Version: 6.7.0-rc8
plugin: installing: https://github.com/dlandon/file.activity/raw/master/file.activity.plg plugin: downloading https://github.com/dlandon/file.activity/raw/master/file.activity.plg plugin: downloading: https://github.com/dlandon/file.activity/raw/master/file.activity.plg ... done plugin: run failed: /bin/bash retval: 1 Updating Support Links
-
Just now, itimpi said:
Are you saying that CA DID offer it as an option? On my test system CA did not offer it while the test system was running 6.6.6.
i agree that if you go direct to gitHub to find the .plg file it will not prohibit you installing it, but I did not envisage people doing that!
i just clicked on the apps tab on the nav bar and found the app and clicked install did nothing strange to get it installed
-
i just clicked install and it installed
-
1 hour ago, trurl said:
Not likely related to your problem, but why are you ignoring this?
Apr 1 06:23:00 Asgard root: Fix Common Problems: Warning: parity.check.tuning.plg Not Compatible with unRaid version 6.6.7 ** Ignored
The reason that plugin is not compatible with your version is because it requires a feature of Unraid that isn't yet available on your version, as mentioned in the first post of the support thread for that plugin:
https://forums.unraid.net/topic/78394-plugin-parity-check-tuning/
1its instaled but disabled just waiting for the update
I've updated the bios and still gettings the errors ill look into changing a PCIe slot but i don't think i can because of clearance issues
i am right in thinking this is pcie slot 1?
that is my gfx card i supose i can remove later down the line
-
im new to unraid and after checking my log file i seem to be getting a few errors and unsure if its important or not
Version: 6.6.7
Apr 1 06:23:56 Asgard kernel: pcieport 0000:00:01.0: AER: Corrected error received: 0000:00:01.0
Apr 1 06:23:56 Asgard kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Apr 1 06:23:56 Asgard kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000
Apr 1 06:23:56 Asgard kernel: pcieport 0000:00:01.0: [ 6] Bad TLP
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: [ 6] Bad TLP
Apr 1 06:25:19 Asgard kernel: pcieport 0000:00:01.0: Error of this Agent is reported first
Apr 1 06:25:19 Asgard kernel: mpt3sas 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 1 06:25:19 Asgard kernel: mpt3sas 0000:01:00.0: device [1000:0087] error status/mask=00000041/00002000
Apr 1 06:25:19 Asgard kernel: mpt3sas 0000:01:00.0: [ 0] Receiver Error (First)
Apr 1 06:25:19 Asgard kernel: mpt3sas 0000:01:00.0: [ 6] Bad TLP
[Support] Djoss - Nginx Proxy Manager
in Docker Containers
Posted · Edited by Dark-Raptor
issue fixed its self
im having with renewing certs also
ive rebuilt the image and re saved all the domains and still no luck
also some domains listed as expired in the SSL page but if i check the site its self it has a newer cert then listed
i have no idea what happened but the issue seems to have fixed its self and all are being renewed now