Now I just recommend Owncloud or seafile. They’re both really easy to install and just work out of the box.

Which one is lighter on your opinion?

How is this possible? I mean, how can they connect the searches from the ip of the server with your laptop’s ip?

And what if the server has a static IP address?

Probably stupid question: let’s say I selfhost searxng only for myself: google & Co can track all my searches, but doesn’t they pair all the data to the IP of my server? And because of this, they will not be able to show personalized ads to me, using my laptop. Is this wrong?

you’re right, thanks for posting it yourself! I’m a newbie in the selfhosting world, so I thought that LibreY was “famous”, but I was wrong!

Why? The public instances are heavily overloaded, isn’t a private instance faster?

Oh wow so really quick! Which NS service did you use? The fields on the bottom of the domain request

Thanks for the info!

When did you request it? And how long did it take for them to activate it after the request?

Oh this is unfortunate :( do you know why?

I’ll look into pp.ua, thanks for the recommendation!

But I know of people running jellyfin on a raspberry, I have an old laptop but it’s not that old… There’srno way to run it smoothly?

You mean a new sever or a new client?

Doing this will prevent my files from seeding, I’d like to find a more “universal” solution

Thanks for the info tho!

So it’s a problem on codecs on my pc, not my server, correct? So installing the correct drivers should solve the issue?

All Mp4 files I tried worked well

I’ll read it as soon as I can, thanks!

How did you solve it?

I found a solution: use myserverhostname.station instead of just the hostname. I really have no idea why, on the previous installation it worked well with just the hostname… ahh, whatever.

thank you very much for the help!

here’s the configuration file for jellyfin:

# ------------------------------------------------------------
# jellyfin.tubbadu.duckdns.org
# ------------------------------------------------------------



map $scheme $hsts_header {
https   "max-age=63072000; preload";
}

server {
set $forward_scheme http;
set $server         "192.168.1.13";
set $port           8096;

listen 80;
listen [::]:80;

listen 443 ssl;
listen [::]:443 ssl;


server_name jellyfin.tubbadu.duckdns.org;


# Let's Encrypt SSL
include conf.d/include/letsencrypt-acme-challenge.conf;
include conf.d/include/ssl-ciphers.conf;
ssl_certificate /etc/letsencrypt/live/npm-18/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/npm-18/privkey.pem;






# Block Exploits
include conf.d/include/block-exploits.conf;








proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


access_log /data/logs/proxy-host-5_access.log proxy;
error_log /data/logs/proxy-host-5_error.log warn;







location / {








proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


# Proxy!
include conf.d/include/proxy.conf;
}


# Custom
include /data/nginx/custom/server_proxy[.]conf;
}

on the server host myserverhostname correctly resolves, but if I enter the container (docker exec -it nginx-app-1 bash) it does not work anymore:

[root@docker-11e3869f946f:/app]# host tserver
Host tserver not found: 3(NXDOMAIN)

(I had to install dnsutils before)

it seems a nginx issue then

how can I find out more about this?

the container has no internet connection at all :(
if I enter in the container shell and try to ping anything it says “bad address”

tubbadu@fedoraserver:~/docker/gluetun$ docker exec -it gluetun sh
/ # ping linux.org
ping: bad address 'linux.org'