tuff_wizard

joined 1 year ago
[–] [email protected] 6 points 7 months ago (1 children)

“Robodebt of medicine” seems like one of the worst metaphors ever conceived.

[–] [email protected] 27 points 8 months ago (5 children)

I know we’ve said it before but THIS year is definitely going to be the year of desktop Linux!

[–] [email protected] 16 points 8 months ago (1 children)

Nice to see a judge with a heart

[–] [email protected] 2 points 8 months ago (1 children)

I mean… they’re not totally wrong.

[–] [email protected] 1 points 9 months ago

No need to be top secret when no one can stop you and you’ve made it almost impossible to live outside the system.

[–] [email protected] 3 points 9 months ago

No idea but there are new and exciting torrent technologies being worked on all the time. Things like DHT nodes or turning off anonymous mode can affect speeds. Your other clients may have different settings enabled or disabled or may not have implemented new protocols.

[–] [email protected] 9 points 9 months ago (2 children)

Can you just give gluetun the wrong info for you vpn server and see if transmission still works?

[–] [email protected] 55 points 9 months ago (2 children)

Figma balls, that is

[–] [email protected] 5 points 10 months ago (3 children)

Nice can you send me the link when you make the torrent?

[–] [email protected] 3 points 10 months ago (2 children)

Well first I’d try turning off pi hole on the server avenue see if it fixes the issue, even though it’s unlikely as pihole should be handling dns requests for your whole network anyway.

Usually with this setup you only need to place your torrent/Usenet download client behind the VPN. Use a container like gluetun and make your download client container a service of gluetun so it only connects though gluetun. The rest of your stack can just access the internet normally.

There should be more info in the jellyseer log file, have a look in your docker directory or have a play with the "docker logs" command and try to recreate the issue. If you kill your jellyseer container then start it

[–] [email protected] 6 points 10 months ago

You have to scroll for miles to reach different sections.

[–] [email protected] 1 points 11 months ago (1 children)
31
submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]
 

Hello

I installed bitwarden via their install script a while back and all was working well.

recently I wanted to start running a reverse proxy because security and also its cooler to type in a domain name instead of numbers. I disabled the ngnix instance that bitwarden had installed because it was hogging the same ports a Ngnix Proxy Manager.

Now how should I get Bitwarden accessable? I have the .conf file from the bitwarden Ngnix instance, can I just load that into NMP somewhere?

or should I just change the ports the old ngnix operates on and point NPM at it when the bitwarden subdomain is accessed?

if it was just one service it would be simple but there are many running in the bitwarden stack, all on the same port and I'm very new to ngnix so I can't fully grasp what the .conf file is doing and I'm unable to add new passwords to bitwarden until I get this sorted out.

Thanks

Edit: bitwarden is in docker container, as is Nginx Proxy Manager

 

Hi All.

I bought It Takes Two through Steam a while ago but only got around to installing it recently. I now realise it uses EA's launcher which is a big piece of shit. Add is some issues linking my EA account to my Steam account and I'm done with it.

It's been a while since I pirated any games, it used to just involve a key gen or copying a few modified files into the right directories.

These days I see whole 'repacks' from fit girls and skid rows.

Is there anything I can do with the game I've already downloaded or do I need to download a repack from someone?

Thanks In Advance.

view more: next ›