[support] Bungy's docker repository

[snowmirage]

On 3/9/2024 at 1:08 PM, snowmirage said:

I think my nzbgetvpn container may have stopped working sometime ago.  I got back to doing some upgrades to my home lab.  I've setup Unraid with multiple VLANs.  I've just moved all my docker containers to one of the new VLANS.  "Network br2.2" 

I can't seem to access the nzbget web ui.

When I look at the logs 

 

2024-03-09 12:57:09,145 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '25361'

2024-03-09 12:57:39,435 DEBG 'watchdog-script' stdout output:
[info] nzbget not running

2024-03-09 12:57:39,435 DEBG 'watchdog-script' stdout output:
[info] Nzbget config file already exists, skipping copy

2024-03-09 12:57:39,447 DEBG 'watchdog-script' stdout output:
[info] Attempting to start nzbget...

2024-03-09 12:57:39,456 DEBG 'watchdog-script' stdout output:
[info] Nzbget process started
[info] Waiting for Nzbget process to start listening on port 6789...

2024-03-09 12:57:39,460 DEBG 'watchdog-script' stdout output:
[info] Nzbget process is listening on port 6789

The service seems to be listening on the port.

and I did update the LAN_NETWORK variable and added all my local networks.

 

I can ping the docker containers IP address (10.2.0.73) and get a response but I get no response at all when trying to access the webgui.  Looking at wireshark, when I try to connect to the webui there's not return traffic at all from the container.

Any ideas what might be wrong here?

Well... I think I fixed it... but I haven't a clue how...

I change the docker container from the above network type to give it an IP address on my VLAN interface (br2.2) to the "Bridge" network type.

after doing this

The UI reports the container has an IP of 172. something.... I have nothing on my network or unraid server using that IP range to my knowledge....



But I happen to try putting in the IP address of my unraid server and the nzbget port in the browser and ... there it is working at 10.2.0.16:6789...

No idea what that did or how its working unfortunately ...

[BoxOfSnoo]

FYI in the latest MySQL image the mysql native password starts up disabled, and `--default-authentication-plugin=mysql_native_password` does not work.  If you're having issues connecting, try adding to the post arguments (advanced mode) `--mysql-native-password=ON`.

[blaine07]

44 minutes ago, BoxOfSnoo said:

FYI in the latest MySQL image the mysql native password starts up disabled, and `--default-authentication-plugin=mysql_native_password` does not work.  If you're having issues connecting, try adding to the post arguments (advanced mode) `--mysql-native-password=ON`.

Thanks for sharing; I had a few things that it evidently borked, invoice ninja, that I hadn't had time to hunt down. No telling what who or how I setup Invoice Ninja that way...sigh LOL

[blaine07]

I wonder if they're going to roll back or what their intentions are/were here? I have a few things I can't get to work even with that argument added - can't remember how I have what setup so I am sure it's a skill issue. Can't downgrade MySWQL Container though can I?

[Frank1940]

On 5/1/2024 at 2:58 PM, BoxOfSnoo said:

FYI in the latest MySQL image the mysql native password starts up disabled, and `--default-authentication-plugin=mysql_native_password` does not work.  If you're having issues connecting, try adding to the post arguments (advanced mode) `--mysql-native-password=ON`.

From the Log file----

 

 

@Bungy, Any thoughts?

[Frank1940]

On 5/1/2024 at 4:01 PM, blaine07 said:

I can't get to work even with that argument added - can't remember how I have what setup so I am sure it's a skill issue.

Luckily, in my case, I found the MYSQL_USER name and the MYSQL_PASSWORD in plain text in the KODI .xml file which made it possible to regain access to the stored MYSQL database.   But I don't can't find (or remember) what the MYSQL_ROOT_PASSWORD password was.  So there is no way for me to get into MYSQL to run any commands that would allow me to change how the password is hashed...