Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.17.0 update to 1.22.0 not working well #196

Open
paineone opened this issue Dec 20, 2024 · 2 comments
Open

1.17.0 update to 1.22.0 not working well #196

paineone opened this issue Dec 20, 2024 · 2 comments

Comments

@paineone
Copy link

paineone commented Dec 20, 2024

Describe the bug
I was using 1.17.0 in a docker container on my Synology Nas with pihole in a macvlan. All worked good, then I thought it is a good idea to update... After recreating the container via portainer from 1.17.0 to 1.22.0 (I deleted .conf file before updating to prevent issues) I can't play clash royale (don't load, always 'wifi' symbol (bad inet connection)), my playstation has issues when I share pics /vids in pan chat (bad DNS setting error) I need to 'try again 12times, then upload beginns....

So I'm back on 1.17.0 now, works well and fast for my playstation and in my sample clash royale game.

Why I become those problems with 1.22.0?
What is mainly changed in 1.22.0 that I become those issues, and why I haven't it with 1.17.0?

It seems 1.22.0 has issues with the upstream or requests (servfail?)

Do I need to change something in the .conf file on 1.22.0 that it works well like in 1.17.0?

@kylekrajnyak
Copy link

FWIW, I'm noticing my own fair share of SERVFAILs which seem to be intermittent. I can't recall ever having this issue before, so perhaps I'll try downgrading and see what happens.

@kylekrajnyak
Copy link

Just wanted to provide an update here to say that I've completely eliminated my SERVFAIL errors by ensuring that cache-min-ttl: 0 and serve-expired: no. Additionally, I ensured that prefetch: yes.

Obviously, your mileage may vary, but in my case at least, it seems many of the domains I frequent had issues with stale cache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants