[Unable to view management console]

8 hours ago, ljm42 said:

 

You probably have DNS Rebinding Protection enabled somewhere. If you were using an unraid.net cert before, then you must have removed that protection from the unraid.net domain. You'll want to do the same thing for the myunraid.net domain.

 

Yea, this was the issue. Under pfsense > Services > DNS Resolver > General Settings in Custom Options, changing

 

server:
private-domain: "unraid.net"

 

to

 

server:
private-domain: "myunraid.net"

 

did the trick. Thanks

[Unable to view management console]

Thanks! I was able to access the gui, upgrade the cert, but cant access via the ipaddress.hash.myunraid.net certificate, just getting a 'can't connect' message on firefox.

 

I've been putting it off, but I guess i'll be upgrading this weekend

[Unable to view management console]

I'm having the exact same issue as OP, I restarted my server and have lost access to the web GUI. https://IPOFSERVER returns a nginx 404 not found page.

 

Fumbled around for a while trying to get it to work, double checking all network connections, pfsense settings, etc. I can't access the GUI boot option either as the video card in the server is passed through to an Unraid VM. Diagnostics were retrieved using telnet.

atlas-diagnostics-20230117-2051.zip

[VM's snapshots]

+1

[[Support] binhex - DelugeVPN]

Hi All,

I've had delugeVPN working great for a long time, but recently added a managed switch and VLANs to the mix and now no matter what, I cannot get DelugeVPN to connect as a download client for sonarr or radarr. When testing the connection i get "Unknown exception: The operation has timed out."

Under DelugeVPN docker settings, if i set VPN_Enabled to NO, sonarr/radarr connects just fine.

 

 

DelugeVPN used to be on its own dedicated port (eth1) but is now on a VLAN network br0.50 sharing the same port as the Unraid main interface.

 

Main interface: 192.168.0.0/24

br0.50: 192.168.50.0/24 (VLAN ID 50)

Bridging is enabled

 

 

 

DelugeVPN Docker Settings:

Network type: Custom br0.50

VPN Enabled: Yes

LAN_Network: 192.168.50.0/24,192.168.0.0/24

gets assigned an IP of 192.168.50.2

 

Sonarr Docker Settings:

Network type: Custom br0.50

gets assigned an IP of 192.168.50.3

 

As far as pfsense goes, i can ping both sonarr and delugeVPN from a separate pc on VLAN ID 50 network. VLAN ID 50 can reach the internet, and the VPN portion of DelugeVPN is working just fine. From the main LAN, i can ping sonarr but not delugeVPN (webUI works fine for both)

 

 

Im new to VLANs, but testing with separate devices everything is working as it should, I'm left thinking theres some setting in Unraid that needs to be tweaked, but not sure what it could be.

 

FYI, I've also tried with Sonarr docker settings: network type Host, and network type Bridge, same issue (only works with VPN Enabled: NO). Any help would be greatly appreciated!

 

 

[[Support] spaceinvaderone - Shinobi Pro]

On 5/15/2020 at 1:06 PM, Sublivion said:

I had the same prob. I created a new database by using mariadb, then just set shinobi to use that location. Then on the next bootup shinobi will create whatever is needed...

Use spaceinvaders nextcloud youtube video as example how to create database using mariadb.

Thought I'd expand on this as it took some time for me to figure out what changes were needed in the shinobi container, and it might help out someone else:

 

Created a mariadb database as follows:

CREATE USER ‘shinobi’ IDENTIFIED by ‘password’;

CREATE DATABASE IF NOT EXISTS shinobi;

GRANT ALL PRIVILAGES ON shinobi.* TO ‘shinobi’ IDENTIFIED BY ‘password’;

 

now you can edit the shinobipro container and make the following changes based on the new mariadb database created above:

 

MYSQL_USER: shinobi

MYSQL_DATABASE: shinobi

MYSQL_HOST: IP address of unraid

maria db database location, change it to: /mnt/user/appdata/mariadb/databases/shinobi/

MYSQL_PASSWORD: password