hathi_ndg
-
Posts
23 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by hathi_ndg
-
-
On 12/30/2019 at 1:55 PM, Djoss said:
Since you are not using the "Bridge" network type, the UI should be reachable over port 8181. In your case you probably need to use http://192.168.2.5:8181
It's been a while, but have you found a solution?
-
How may I setup the built-in Wireguard VPN server feature so that my qbittorrent traffic goes through it and remains hidden from outside eyes? For the life of me I've been searching for weeks and can't find a clear answer thanks so much for any help!
-
ok I just got my issue fixed
**Reminder: the affected containers were all hotio's
Credit: found the solution here:
Example with my sonarr container:
Replaced with:
"Apply", wait and "Done"
-
On 2/13/2024 at 8:13 AM, g0nz0 said:
Forcing a re-download of the container by adding / canging a dead envrionment variable will force it to update, but it's impossible to say if it's needed on any given 'broken' container at present.
Hi! How do you do this?
I'm on 6.12.8 and still got the "Not available" message under "Version" for 3 containers, which are all hotio's containers too. Will dig into it
thanks!
-
3 minutes ago, ConnerVT said:
Try asking in the support thread of your docker in the Docker Container sub-forum.
Actually it's not a Docker container, it's the Built-In VPN feature under Settings -> VPN Manager
-
Hi! Anyone has a hint or 2?
been looking around for answers, but no luck, thanks so much!
-
Thanks!You need to put the following in the "Extra Parameters" section of the app/container you want to route through the VPN app/container "--net=container:OpenVPN-Client" replacing the "OpenVPN-Client" in the example with the exact name you have for that app/container. It's likely very close to the example provided. but likely has AIO in the name. Put that in your qBittorrent app configuration and it'll route all traffic through the VPN app container.
Sent from my Pixel 5 using Tapatalk
- 1
-
I'm having the same issue, watching for replies!
Sent from my Pixel 5 using Tapatalk -
I'm quite new in trying to understand how Unraid built-in VPN feature works.
My need: I want traffic from my QBittorrent docker container to run through a VPN connection so traffic is hidden from unwanted attention.
Some things I can't figure out, please bear with me:
In Settings > VPN Manager, does this allow me to create a VPN server? Or does this interface allow me to connect to a VPN service? Do I need to be already subscribed to a VPN provider in order to use this?
thanks, I might have follow-up questions depending on the answer, thanks so much for any help.
-
Just installed OpenVPN AIO Client, now how can I make sure the traffic from qbittorrent goes through it?
-
any development on this? I have the same issue here :/
-
15 hours ago, ljm42 said:
The syslog has multiple call traces that look like this:
Sep 10 22:38:04 Tower kernel: Call Trace: Sep 10 22:38:04 Tower kernel: <IRQ> Sep 10 22:38:04 Tower kernel: dump_stack_lvl+0x44/0x5c Sep 10 22:38:04 Tower kernel: __report_bad_irq+0x35/0xaa Sep 10 22:38:04 Tower kernel: note_interrupt+0x1f6/0x24d Sep 10 22:38:04 Tower kernel: handle_irq_event_percpu+0x2c/0x35 Sep 10 22:38:04 Tower kernel: handle_irq_event+0x37/0x56 Sep 10 22:38:04 Tower kernel: handle_fasteoi_irq+0x99/0x113 Sep 10 22:38:04 Tower kernel: __common_interrupt+0x9e/0xaa Sep 10 22:38:04 Tower kernel: common_interrupt+0x96/0xc1 Sep 10 22:38:04 Tower kernel: </IRQ> Sep 10 22:38:04 Tower kernel: <TASK> Sep 10 22:38:04 Tower kernel: asm_common_interrupt+0x22/0x40 Sep 10 22:38:04 Tower kernel: RIP: 0010:cpuidle_enter_state+0x11d/0x202 Sep 10 22:38:04 Tower kernel: Code: 20 22 a0 ff 45 84 ff 74 1b 9c 58 0f 1f 40 00 0f ba e0 09 73 08 0f 0b fa 0f 1f 44 00 00 31 ff e8 4c e3 a4 ff fb 0f 1f 44 00 00 <45> 85 e4 0f 88 ba 00 00 00 48 8b 04 24 49 63 cc 48 6b d1 68 49 29 Sep 10 22:38:04 Tower kernel: RSP: 0000:ffffc900000dbe98 EFLAGS: 00000282 Sep 10 22:38:04 Tower kernel: RAX: 0000000000000000 RBX: ffff888353bf6300 RCX: 0000000000000020 Sep 10 22:38:04 Tower kernel: RDX: 00000000820ed4af RSI: 000000007fffffff RDI: 00000000ffffffff Sep 10 22:38:04 Tower kernel: RBP: 0000000000000004 R08: 0000000000000002 R09: 0000000000000002 Sep 10 22:38:04 Tower kernel: R10: 0000000000000020 R11: 0000000000000004 R12: 0000000000000004 Sep 10 22:38:04 Tower kernel: R13: ffffffff823205c0 R14: 000000010624b113 R15: 0000000000000001 Sep 10 22:38:04 Tower kernel: ? cpuidle_enter_state+0x117/0x202 Sep 10 22:38:04 Tower kernel: cpuidle_enter+0x2a/0x38 Sep 10 22:38:04 Tower kernel: do_idle+0x18d/0x1fb Sep 10 22:38:04 Tower kernel: cpu_startup_entry+0x1d/0x1f Sep 10 22:38:04 Tower kernel: start_secondary+0x101/0x101 Sep 10 22:38:04 Tower kernel: secondary_startup_64_no_verify+0xce/0xdb Sep 10 22:38:04 Tower kernel: </TASK> Sep 10 22:38:04 Tower kernel: handlers: Sep 10 22:38:04 Tower kernel: [<(____ptrval____)>] usb_hcd_irq Sep 10 22:38:04 Tower kernel: [<(____ptrval____)>] usb_hcd_irq
Those do not look like normal "call traces related to macvlan". But it wouldn't hurt to switch from macvlan to ipvlan anyway, see https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-tracesThanks I'll look into that!
**Edit: done!**
Let's see how this rolls, along with my RAM sticks 1 by 1 testing!
-
--> Changed the USB flash drive for a brand new one, transferred the key, etc.
--> Removed corefreq ans swapfile
Result: Still crashed after 3-4 minutes
--> Testing RAM sticks 1 by 1 now. Will update here.
** Stick 1/6: ran smoothly for 17 hours 45 minutes ✅
** Stick 2/6 : 2 hours 20 minutes of smooth sailing ⏲️
Meanwhile, if anyone has hints with the diagnostics or syslog, lmk
thanks!!
-
On 10/21/2022 at 1:11 PM, endystrike said:
Hi everyone,
my ISP activated me the public IP, if I try both from my smartphone (after disabling wifi) and from my PC to enter via web browser into my Unraid, it works...
But I don't know why, when I do the test from Unraid it says that the server is not reachable from the internet.
I tried to also test the connection and everything seems to be fine: the NAT forwarding works as expected forwarding the traffic from external port 52890 to internal port 443 on Unraid's IP.
If I try from the web browser, everything seems to be fine too.
Now, I've 2 questions:
1) I put a domain under cloudflare and enabled proxy: but if I try to reach the host using the fqdn, it doesn't work... I'm using Cloudflare DDNS docker and the IP in Cloudflare matches with the real one, so the docker is working properly... Why I cannot use my fqdn? Is there any particular setting in Cloudflare that should be set?
2) Why unraid under settings is telling me that my server cannot be reached from the internet when I can enter into it from https://mypublicip:52890?
I attach here the diagnostic too.
endys-diagnostics-20221021-1910.zip 108.25 kB · 1 download
Thanks a lot for your help guys!
Hi ! I got the same situation at the moment, what was your resolution?
-
And crashed now while mounting remote shares (looks like it though)
-
ok it re-crashed about 5 minutes ago, Here are the new diagnostics as well as the syslog that's fed continuously on the flash drive
-
Hi, I've been setting up my first server last Spring, mainly for torrenting and running Plex.
Since 2-3 months, it keeps crashing randomly. I've tried to pinpoint the issue, with no success.
It crashes in safe mode too.
Recently, I notice it crashes after in enable Docker. I'll need to troubleshoot to see if it crashes with Docker disabled too.
**Edit** It crashes in Safe Mode too (after 3 minutes)
Hard drives and SSD are new from last Spring (maybe one is older, not sure)
(I attached today's syslog and Diagnostics)
Things I know:
- Memtest ran flawlessly for 20 hours
- CPU stress tests with corefreq also runs perfectly
- SMART tests return no errors on all drives
- CPU and RAM are not OC'd, everything runs with factory settings/frequency and such
Some Specs:
OS version: 6.12.4
MB: EVGA X58 SLI LE
CPU: intel core i7 920 2.67MHz
RAM : 6x OCZ 1333MHz 2Gb DDR3
Any help would be greatly appreciated, thanks!
-
17 minutes ago, PerfectlyCromulent said:
It turned out to be my USB. Bought a new one and it hasnt crashed once.
Ok I'll definitely check that out too, thanks!
I noticed I've never done any balance or scrub on my btrfs ssd cache drive, doing it live.
cheers!
-
Hi! Any resolution? I'm experiencing the same crashing after 3 minutes in. Ran flawless memtest (20 hours), SMART tests on all drives and CPU torture sessions.
CPU + RAM are not OC'd either. -
Hi, any resolution? I'm experiencing the same crash after 3 minutes in, memtest and recent SMART tests ended up flawless. CPU & Ram are not OC'd either.
-
Thanks I'll check this out!
-
Hi all, this is my first post here. I set up my server approx 2 months ago. I use it for torrenting, learned a lot, now everything seems to be properly set up since a month, I'm super satisfied with Unraid.
I got that error last night, and saw that I should post my diagnostics here. So here they are.
At the moment, looking at my memory levels, nothing seems full, but the warning remains, wondering why.
thanks for any hint, cheers!
Possible SYN flooding on port 41083
in General Support
Posted
Any development on that issue? I'm seeing the same message :
Tower kernel: TCP: request_sock_TCP: Possible SYN flooding on port 50113. Sending cookies. Check SNMP counters.
...in my logs and have no idea how to act on it. Since I'm not _that_ advanced to follow the https://access.redhat.com/solutions/30453 instructions, is there any rookie-friendly way on finding out what can cause these messages?
thanks a lot!