-
Connecting Open WebUI and Papeless-ai to ollama
I was also struggling to get ollama talking to Open WebUI, the template for ollama has changed since spaceinvaderone's video. Now instead of the port number in ollama template you need to enter: http://0.0.0.0:11434. In Open WebUI template, for the Ollama base url enter: http://[serverip]:11434. Ensure in Open WebUI under settings, connections Ollama API connections is set to http://[serverip]:11434.
-
Change Unraid's behaviour when array device is disabled
Hi All, I've looked through the Unraid docs and scoured the settings, so thought I'd ask here. Every now and then i get a disk that drops from the array, I've replaced the cable but still happens every now and then. When it does happen, I have to rebuild the data to the drive once it's connected again which takes days as the drives are 16TB and causes unnecessary wear and tear. When a disk is dropped, is there any way to tell Unraid to just stop the array instead of disabling the disk and continuing on with an emulated disk?
-
[Support] binhex - DelugeVPN
I'm having a similar issue, just updated all dockers and now binhex-delugevpn, binhex-lidarr and binhex-jacket which all run on a custom network fail to get an IP address or webui. all other containers on the custom network continue to work just fine. But switching from custom network (VPN) to host does nothing. Nowhere in the logs does it mention a 192.168.50.xxx ip address (custom br0.50 network) 2024-12-08 21:44:34,379 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2024-12-08 21:44:35,141 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address **MY VPN EXIT IPV4** 2024-12-08 21:44:35,142 DEBG 'start-script' stdout output: [info] VPN provider 'airvpn' not supported for automatic port forwarding, skipping incoming port assignment 2024-12-08 21:44:35,178 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP **MY VPN IPV4** different, marking for reconfigure 2024-12-08 21:44:35,180 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2024-12-08 21:44:35,182 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2024-12-08 21:44:35,184 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2024-12-08 21:44:35,185 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2024-12-08 21:44:35,293 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '**MY VPN IPV4**' [info] Deluge key 'listen_interface' will have a new value '**MY VPN IPV4**' [info] Writing changes to Deluge config file '/config/core.conf'... 2024-12-08 21:44:35,408 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'tun0' [info] Deluge key 'outgoing_interface' will have a new value 'tun0' [info] Writing changes to Deluge config file '/config/core.conf'... 2024-12-08 21:44:35,533 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of 'xxxxxxxxxxxxxxxxx' [info] Deluge key 'default_daemon' will have a new value 'xxxxxxxxxxxxxxx' [info] Writing changes to Deluge config file '/config/web.conf'... 2024-12-08 21:44:35,555 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2024-12-08 21:44:35,772 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2024-12-08 21:44:36,978 DEBG 'watchdog-script' stderr output: <Deferred at 0x1471d99422d0 current result: None> 2024-12-08 21:44:37,011 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2024-12-08 21:44:37,011 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2024-12-08 21:44:37,012 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2024-12-08 21:44:37,012 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2024-12-08 21:44:38,015 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2024-12-08 21:44:38,018 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118
jevan223
Members
-
Joined
-
Last visited