Boo-urns
-
Posts
59 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Boo-urns
-
-
On 1/21/2020 at 1:53 AM, Hanky said:
Would like to request this GIT:
https://github.com/keshavdv/unifi-cam-proxy
Adding non unifi cameras to unifis NVR
Hey mate, did you end up getting anywhere with this? I'm trying to get my non-Unifi cams working with my UDM-Pro and this seems perfect. Can't quite figure out the docker template though, although the docker is here if someone can help.
-
Can anyone provide any assistance on this, or at least point me to where I can find some pls?
-
I've been getting these 'Out of Memory' errors every few days, which seems to be related to the log filling up I believe.
I've posted the diagnostics below as per the Fix Common Problems suggestion. If anyone could have a look to see the cause, and suggest a potential fix that would be greatly appreciated.
TIA.
-
1 hour ago, ljm42 said:
Also, why are you ignoring the warning that the local endpoint you entered doesn't resolve to the correct IP?
It resolves to the correct IP. I just have it set to my DDNS address, which resolves to my public IP.
I have the static route set, host access enabled and Use NAT=No, however cannot access custom networks. These being other VLANs, DelugeVPN docker (which is set to bridge network), my CCTV VLAN. All of these I can access when connected to my LAN normally.
-
4 hours ago, ljm42 said:
Everyone's setup is different. Go to the VPN Settings page, enter advanced mode, and show a screenshot of the static route it tells you to setup.
Attached. Seems right, but isn't working. So I need to set up firewall rules also?
-
Greeting again.
Can anyone confirm this is the correct Static Route I need to set in a Unifi router? I still cannot access custom networks from my WG client. Normal LAN is fine.
-
6 hours ago, ich777 said:
Thank you for that, I don't think the TBS-OS drivers support this card, only the LibreELEC build.
I only can tell you that my DVBSky tuners in my dev machine work just fine with LibreELEC build and those are CX23885 based:
Have you changed anything on your hardware recently? Motherboard, CPU,...?
If this is a AMD system please look if a BIOS update is available.
I find only similar errors for the CX23885 based Hauppauge tuners and those mention about turning of IOMMU in the BIOS.
Yeah I've reinstalled the LibreELEC drivers and it's recognised again.
My system is a Ryzen system (R7 1700) and I did upgrade the motherboard about 2 months ago. I do remember an IOMMU setting in the BIOS. So that should be turned OFF?
-
2 minutes ago, ich777 said:
What is the output of 'dmesg' (please put the output in a textfile and drop it here in the textbox).
Try to do a 'modprobe cx23887'
dmesg attached.
modprobe returned:
modprobe: FATAL: Module cx23887 not found in directory /lib/modules/5.10.28-Unraid -
On 4/30/2021 at 5:04 PM, ich777 said:
Can you try to remove the line from your syslinux configuration again and select the TBS-OS source drivers and reboot after that?
I've found a few reports on Google after searching for that specific error, just put this line in the Google search text box:
linuxdvb: Silicon Labs Si2168 #2 : DVB-T #0 - poll TIMEOUT
Seems like the TBS-OS drivers support your card too.
I've deleted the plugin, reinstalled, rebooted, selected the TBS-OS drivers and rebooted, and my card is not recognised at all. Do I need to do something specific to get the TBS drivers to work?
Card is still listed however in 'lspci -v' output:
0d:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04) Subsystem: Hauppauge computer works Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb Flags: bus master, fast devsel, latency 0, IRQ 11, IOMMU group 14 Memory at fc400000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] Power Management version 3 Capabilities: [90] Vital Product Data Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Advanced Error Reporting Capabilities: [200] Virtual Channel 0e:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04) Subsystem: Hauppauge computer works Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb Flags: bus master, fast devsel, latency 0, IRQ 10, IOMMU group 14 Memory at fc200000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] Power Management version 3 Capabilities: [90] Vital Product Data Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Advanced Error Reporting Capabilities: [200] Virtual Channel -
46 minutes ago, ich777 said:
Is this your card: Click?
Yep that's my card.
I've tried and only the libreelec driver actually recognise my card.
46 minutes ago, ich777 said:Can you try to append this to your syslinux.cfg: 'cx23885.dma_reset_workaround=2'
I've added the line as above and rebooted but it doesn't seem to have any effect. Some channels play, others don't, but there is a repeating error in the tvheadend docker log:
2021-04-30 16:13:06.752 [WARNING] linuxdvb: Silicon Labs Si2168 #2 : DVB-T #0 - poll TIMEOUTThe same channel plays fine when connected to a TV directly.
Any other suggestions or logs I can pull?
-
6 hours ago, ich777 said:
Are you using the LibreELEC drivers?
You can't roll back to a different version because they are pretty much the same and I only have to compile them for every Unraid version.
What you can do is to downgrade to the Unraid version that you think it worked before and try it again.
The LibreELEC drivers are not much different from the versions before.
Can it be that there is a physical problem with the cables?
Yes I'm running the LibreELEC drivers.
I tried to eliminate the cable as the fault, by using another cable, however problem persists. Plus plugging the cable directly to a TV plays OTA channels perfectly.
Would downgrading Unraid make any difference? What effect would that have?
Also, would the DigitalDevices or TBS devices work with my Hauppage card?
Is it possible my card itself is being flaky?
Sorry for the million questions, I'd really like to resolve this issue.
Is there any other troubleshooting I could do?
-
I've been having issues recently with my TV Tuner. I use a Hauppage QuadHD PCIe card, backend tvheadend, via 'antennas' to Plex (all in dockers). Some channels will not tune while others do, later on they'll be fine and others will fail. Using different tuners (1,2,3 or 4) for the playback sometimes works, sometimes doresn't. I haven't had this specific issue before, and just seems to have started recently (since around the 6.9.1/6.9.2 unraid version releases).
dmesg output seems to include the below errors several times, but no idea what they mean.
[166371.596864] AMD-Vi: Event logged [IO_PAGE_FAULT device=0e:00.0 domain=0x000f address=0xbd7ed1c8 flags=0x0000] [166371.632766] cx23885: cx23885[1]: mpeg risc op code errorLike I said, I haven't had these errors before that i'm aware of, but could be it due to updated drivers? Can I roll back?
tvheadend throws lots of errors in the log too, including "invalid checksum", "continuity counter error" and "transport errors" when it doesn't play.
This is really driving me nuts, and the WAF of my network TV system is dropping significantly each day this keeps failing.
Any help would be greatly appreciated.
-
OK, randomly after a few reboots it magically showed up in router devices and I could login to the webGUI. I thought perhaps my previous pfsense VM could be contributing, so I disabled VMs and set PCIe ACS Override back to disabled. I rebooted and once again network was down during boot and unreachable.
I did notice that the network activity light on the mobo LAN connection intermittently turned off completely, where otherwise it staying flashing Gb connection. So I thought perhaps faulty cable? Replaced cable no change. Faulty LAN port maybe?
I restored a previous flash backup, which didn't actually change anything because it updated to Unraid.net during the brief period it was working. But it booted somehow.
I created a bond between my mobo LAN port (eth0) and my 4 port PCIe NIC (eth1) and made them redundant (mode 1), so I could test whether it was the mobo LAN port, but since then I haven't had it fail.
Attached are current diagnostics with Unraid working, and obviously the above diags are from when unraid was not booting (network down).
The only thing I can think of is if the motherboard ethernet port was intermittently failing, in which case i'd be looking to RMA as it's only a few months old. However if it's an Unraid issue i'd love to know what was causing it so I can avoid this in future.
If you can make sense of the logs it would be appreciated.
-
12 minutes ago, trurl said:
Get us new diagnostics from command line as explained here
OK, randomly after a few reboots it magically showed up in router devices and I could login to the webGUI. I thought perhaps my previous pfsense VM could be contributing, so I disabled VMs and set PCIe ACS Override back to disabled. I rebooted and once again network was down during boot and unreachable.
I did notice that the network activity light on the mobo LAN connection intermittently turned off completely, where otherwise it staying flashing Gb connection. So I thought perhaps faulty cable? Replaced cable no change. Faulty LAN port maybe?
I restored a previous flash backup, which didn't actually change anything because it updated to Unraid.net during the brief period it was working. But it booted somehow.
I created a bond between my mobo LAN port (eth0) and my 4 port PCIe NIC (eth1) and made them redundant (mode 1), so I could test whether it was the mobo LAN port, but since then I haven't had it fail.
Attached are diagnostics from when unraid was not booting (network down), and currently working.
The only thing I can think of is if the motherboard ethernet port was intermittently failing, in which case i'd be looking to RMA as it's only a few months old. However if it's an Unraid issue i'd love to know what was causing it so I can avoid this in future.
If you can make sense of the logs it would be appreciated, and massive thanks for your help so far (my RAM is back down to 15%. Hooray!
skynet-diagnostics-20210422-2304 (not booting).zip skynet-diagnostics-20210424-1103 (working).zip
-
14 hours ago, trurl said:
Are you sure you booted in GUI mode? Can you login at that screen?
Sorry, for clarity, booting to GUI Mode (and GUI Safe Mode) shows the login screen, but i'm unable to enter text to try and login.
-
@Squid Additionally, booting to GUI Mode (and GUI Safe Mode) shows the login screen, but i'm unable to enter text to try and login.
-
11 hours ago, trurl said:
Are you sure you booted in GUI mode? Can you login at that screen?
I booted in normal mode (no GUI) and can login via the terminal directly. But it not available over network and won't boot in GUI mode.
-
2 hours ago, Squid said:
If it's showing Tower Login and the wall of text is still there, then you booted normally, and not via the GUI mode. GUI mode is an option from the webGUI over the network
login with root and your password and then enter in
diagnosticsIf you can reach your shares over the network, then grab the diagnostics file that's saved on the flash share in the logs folder and post it here
If not, then
powerdownpull the flash toss it into another system and post it here
logged in with root and ran "diagnostics". Saved file attached.
Was not available over the network so this was taken directly from flash.
Cheers @Squid. Server is unusable currently so any help would be appreciated.
-
So I've just done a reboot and now the server UI isn't accessible at all. Device doesn't show up in router devices (has a static IP set in Unraid).
Boot screen (black screen/white text) gets to tower login, but GUI doesn't load. I did notice it mentioned eth0 not found during the boot sequence whether that affects it.
Not sure what has broken it, but any suggestions to troubleshoot? I've tried safe mode with/without GUI with no luck.
Prior to rebooting I had my rootfs 95% used, and high RAM usage, which I think was due to Plex transcoding to /tmp. I cleared the variable and rebooted to clear RAM and now I'm stuck. Any ideas?
-
1 hour ago, trurl said:
reboot
So I've performed a reboot and now the server UI isn't accessible at all. Device doesn't show up in router DHCP either.
Boot screen (black screen/white text) gets to tower login, but GUI doesn't load. I did notice it mentioned eth0 not found during the boot sequence whether that affects it.
Not sure how this has broken it, but any suggestions to troubleshoot? I've tried safe mode with/without GUI with no luck.
-
14 hours ago, trurl said:
Diagnostics shows rootfs 95% used. Something must be writing to RAM. The OS is in RAM, so anything that specifies a path that isn't to actual storage (some subfolder of /mnt) is a path in RAM. Check each Host Path for each of your containers.
So I found my Plex transcoding directory was mapped to /tmp, so this was probably causing it. This has been changed now. Would a restart delete the ram usage or do I need to manually remove files?
-
So I've had a few issues recently where the server would crash, which seemed to be because it ran out of RAM (I managed to log in and most dockers were stopped with errors, and RAM was almost 100% of 32GB).
I've noticed my RAM usage seems to be stable-ish at roughly 70%, but that's way more than usual.
How can I diagnose what is using all the RAM, and potentially fix it? I've looked at the advanced docker tab with RAM/CPU usage and nothing stands out.
Edit: Completely stopping the docker service only drops usage to 60%. Only other running thing is Pfsense VM with 3GB allocated.
-
3 hours ago, bonienl said:
- WG configuration -> Local server uses NAT = No
- Docker configuration -> Host access to custom networks = Enabled
- The router needs a static route to forward the WG subnet (10.253.0.0/24) to the Unraid server (192.168.1.x)
I had these settings sorted already, including the static route. I've added the simplified AllowedIPs subnet on the client with no effect. Below is the static route set. Does anything glaring obvious stand out that i've done incorrectly? Unraid IP is 192.168.1.4.
On 4/3/2021 at 3:31 PM, Boo-urns said:
Unraid settings as follows:
Thanks again for your help.
-
6 hours ago, bonienl said:
Delete all tunnels and start from scratch (choose Remote access to LAN for the peer), this will generate a peer config similar like
Remote peer configuration [Interface] #My iPhone PrivateKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx= Address=10.253.0.2/32 [Peer] #My Unraid server PublicKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx= Endpoint=www.mysite.com:51831 AllowedIPs=10.253.0.1/32, 192.168.1.0/24Load this config on the peer and add manually the additional networks, like 192.168.2.0/24, 192.168.3.0.24, etc to the list of AllowedIPs using the WG app on the peer (do not delete the existing entries).
OK so i've done exactly this. I have a LAN connection via WG and can access everything normally, except for VLANS and custom dockers.
eg I have a Shinobi docker running on VLAN5 (192.168.5.2) with all CCTV cams as well which timeout on WG. Additionally, DelugeVPN and Jackett (routed through DelugeVPN) are not accessible either.
All of the above are accessible normally via this PC (192.168.1.5).
Would there be any other specific routing required?
[Support] Djoss - Nginx Proxy Manager
in Docker Containers
Posted · Edited by Boo-urns
OK so i'm pulling my hair out here.
I'm trying to expose a Wordpress docker to the internet via Nginx Reverse Proxy (NPM).
I currently own a domain, use cloudflare, and have a NPM docker handling the proxying. For example, currently have mydomain.com going to overseerr (serverip:5055), and nextcloud.mydomain.com going to nextcloud (serverip:444). Router fwds port 443 to npm. I have 'force SSL' on cloudflare enabled, so haven't even opened port 80. Working fine, no problem. Have used the ibracorp tutorial for this process here.
Decided to try and host a site using Wordpress (complete noob with wordpress btw), set it up the same as I had with nextcloud using these steps:
Not working! I'm just getting a timeout when attempting to access wp.mydomain.com. Via LAN accessing 192.168.1.4:8282 shows the WP test page perfectly, but no idea why this isn't working via proxy.
I've tried recreating my SSL certificates, forwarding to a different docker (heimdall for example), with same result.
I'm not sure what i'm doing wrong, particularly because I already have 2 working proxies, but if anyone could point me in the right direction i'd be forever grateful. TIA