[[Support] Gitea]

Just installed this container. I couldn't access the web interface until i edited the file /appdata/gitea/gitea/conf/app.ini

(Default settings do not work)

Changed

[server]
APP_DATA_PATH = /data/gitea
DOMAIN = x.x.x.x
SSH_DOMAIN = x.x.x.x
HTTP_PORT = 8300
ROOT_URL = http://x.x.x.x:8300/

to:
 

[server]
APP_DATA_PATH = /data/gitea
DOMAIN = x.x.x.x
SSH_DOMAIN = x.x.x.x
HTTP_PORT = 3000
ROOT_URL = http://x.x.x.x:8300/

So it matches the default container HTTP port of 3000

[[Plugin] FolderView]

On 1/16/2024 at 8:47 PM, scolcipitato said:

This is my last idea, if this doesn't work, I don't know what to do.

Made a new version, if you want to give it a try you can.

That update fixed it!
Thanks very much @scolcipitato

[[Plugin] FolderView]

Reinstalled again - still no difference

[[Plugin] FolderView]

Thanks - I tried the update but there is no change

[[Plugin] FolderView]

Thanks @scolcipitato - I can't think of any other plugin I have which would change the webui - any idea how to find what it would be? After I removed folder view - the order of my VMs is as follows (not the same as the list from the debug file)
 

1  Centum_FT
2  CodeSys T11
3  Fast Tools Stardom
4  GeoSCADA2020
5  Geo SCADA 2021
6  HA Dev
7  Home Assistant HAOS
8  Macinabox Catalina
9  SimaticTIA17Pro
10  SimaticTIA17Unified
11  StardomT11
12  Tiny11_2311
13  Windows 10 Gaming
14  Windows 11

 

[[Plugin] FolderView]

13 hours ago, scolcipitato said:

I need the debug file (first post for instructions)

debug-VM.json

[[Plugin] FolderView]

In my VMs tab - the wrong VMs show in the configured folder. Docker folders work fine.

Screenshots show config and Folder View Display - as you can see different VMs from those selected appear in the "Home Automation" folder.
Any idea how to fix this? I have tried both Firefox and Edge - same problem.

 

 

[[Support] Linuxserver.io - Plex Media Server]

10 hours ago, rmeaux said:

Been running "latest" for as long as I can remember. I woke up this morning to a bunch of "unable to start server: sqlite3..........." errors. An appdata restore didn't resolve anything. But changing "latest" to the previous release "1.32.0.6950-8521b7d99-ls163" resolves the database corruption and Plex works fine. Anyone els having issues with "1.32.0.6973-a787c5a8e-ls164"?

Same issue - thanks for your fix. First tried Spaceinvader's fix (https://www.youtube.com/watch?v=2ZDX7Gq7UFU ) unsuccessfully.

 

[[Support] binhex - DelugeVPN]

My VPN is failing to connect within 60 seconds and I receive the following error:

TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

When I test the VPN connection on my Windows laptop using the VPN provider's OpenVPN client - it takes nearly 90 seconds to create the connection

OpenVPN.Control - INFO - Connection built in 80.815 sec.

 

Is there any way I can extend the timeout to say 120 seconds?

[[support] Vaultwarden (formerly Bitwarden_rs)]

On 8/18/2020 at 12:37 AM, carltonb said:

I have no clue if this is the correct area to post this but I need some help with Bitwardenrs.

I have it installed for the last 3 months and is working well. Got all my family tied into it so we are all happy.

Now my problem comes with using 2FA. I use a YubiKey for 90% of all my 2FA, but it seems that it does not play nice with Bitwardenrs.

It will not recognize certain aspects odf the YubiKey, like otp. And as well it it gives me time sync errors.

I did find a piece of docker code they said that needs to be installed but I do not know how to do it on unRaid.

docker run -d --name bitwarden \
  -e YUBICO_CLIENT_ID=12345 \
  -e YUBICO_SECRET_KEY=ABCDEABCDEABCDEABCDE= \
  -v /bw-data/:/data/ \
  -p 80:80 \
  bitwardenrs/server:latest

Can anyone shed some light on this for me.

Thanks so much

@carltonb I have just got this working. You need to:

• Follow the instructions at this link to get values for YUBICO_CLIENT_ID and YUBICO_SECRET_KEY.
• In UNRAID - open the settings for the bitwardenrs Docker container
• At the bottom click on "Add another Path, Port, Variable, Label or Device"
• Set Config Type = Variable, Name = YUBICO_CLIENT_ID, Key = YUBICO_CLIENT_ID, Value = <Your Yubico Client ID>
• Click Add
• Add another variable as above for YUBICO_SECRET_KEY
• Click APPLY to restart the Docker container

That should be it - now you can configure the Yubikey in the Bitwarden Settings.