fithwum

this it not the support thread for that docker that is not my docker you need to contact ich777

Support for Minecraft server docker Application: Minecraft Application Site: https://www.minecraft.net Docker Hub: https://hub.docker.com/r/fithwum/minecraft/ Github: https://github.com/fithwum/minecraft/ This is a simple Minecraft server, the default tag will be whatever the latest server version is available but you can select a specific version going back to 1.16 if you want. I am working on a forge version as well Please post any questions/issues relating to this docker you have in this thread.

It is available you just need to add the :alpine tag to it now so the new repository is fithwum/foundry_vtt:alpine because of the changes i have made to it for adding other versions and things

for some strange reason mine is working again. could be from rebooting the server or reinstalling the docker i don't know

i have the same problem and it just started the docker sees the GPU no problem just will not use it and no idea why. it was working the other day.

i did have the same problem as you but cant for the life of me remember how i fixed it. i will try and find how i did it and get back to you

your site seems to load just fine. in an older post i put up my working proxy config for swag you could have a look at that and see the difference with yours

what version incompatibilities are you running into? Most things can be updated from within the app itself i think even foundry can update from inside now.

this is not a docker problem this is a teamspeak problem, you would need to access the serverquery to fix this.

I am not sure why that is happening the update is working fine on my system. the error is normally an unraid error as far as i know

you should also be able to set your network to bridge and change the port that way. i run mine through swag and they have a config for foundry now i think.

still getting the error after update and fix but at least it works again

Server gets to this and seems to stop and nothing further. Valheim Log.txt

My group uses TeamSpeak3 and sometimes nextcloud talk.

I have mine on a custom proxynet for use with swag, you might be able to run that way to have 2 instances running. Glad to see you got it working tho

i did it based on the Linux version and that works well, but from what i can tell the node.js one could work as well

i dont know on that one i will have to have a look at it and test it on my system and get back to you

there are earlier posts that have configs that work. I did post one that works with swag and i might work for you.

worth a shot thanks for the info i will try it today and push out an update EDIT: Seems to work well will try over the next few days but update is out now for the docker.

looks like you might be using an old config that has a problem with swag if you scroll up a bit you should see another post i made with an updated one that works you just need to rill in the relevant info for your setup

to update the version of foundry you can click the update button in foundry and it will work the docker has no control over what version you are running or you can shut down the docker and update the files yourself using a file explorer.

Im glad that worked

sounds like a reverse proxy error that i ran into. This is my proxy config that works with swag. server { listen 443 ssl; listen [::]:443 ssl; server_name foundryvtt.*; # Listen on port 443 using SSL certificates ssl_certificate "/etc/letsencrypt/live/"PUT URL HERE"/fullchain.pem"; ssl_certificate_key "/etc/letsencrypt/live/"PUT URL HERE"/privkey.pem"; include /config/nginx/ssl.conf; #add_header Referrer-Policy "same-origin" always; #add_header Access-Control-Allow-Origin https://foundryvtt."PUT URL HERE" always; client_max_body_size 1024M; fastcgi_buffers 64 4K; location / { #enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; #enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; # Set proxy headers proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; # These are important to support WebSockets # proxy_set_header Upgrade $http_upgrade; # proxy_set_header Connection "Upgrade"; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app FoundryVTT; proxy_max_temp_file_size 1024m; proxy_pass http://$upstream_app:30000; } } # Optional, but recommend. Redirects all HTTP requests to HTTPS for you server { if ($host = foundryvtt."PUT URL HERE") { return 301 https://$host$request_uri; } listen 80; listen [::]:80; server_name foundryvtt."PUT URL HERE"; return 404; }

like i said you could try a different service Top Alternatives to Cloudflare Amazon CloudFront. Fastly. Microsoft Azure CDN. Imperva Cloud Application Security. KeyCDN. Sucuri. Akamai. StackPath CDN. This is the list Goole gives fo other options

might be CloudFlare you might try a free service to test it also if you are using a reverse proxy it might be that. i was using CloudFlare myself but had to stop as it was giving me problems.