

thanks a lot problem solved
thanks a lot problem solved
changed it! thanks a lot!
thanks a lot!
thank you! this works!
no I don’t think pi-hole supports wild card dns, how do you deal with this issue? do you simply use addguard?
thank you problem solved!
thank you! this works!
thank you! this works!
Thank you! Can you also explain the difference between
networks:
default:
external: true
name: scoobydoo
and
networks:
scoobydoo:
external: true
I think they are? I have used network setting in audiobookshelf
networks:
nginx:
name: nginx-proxy-manager_default
external: true
I think this allows audiobookshelf container to use the external container generated by nginx by default
thank you!
I have added
ports:
- 13378:80
in audiobookshelf docker compose and changed npm settings
But it still gives me the same 502 Bad Gateway error.
I have turned it off and tried again, this time it allows me to go to http://audiobookshelf.local.com/, however still giving me the 502 Bad Gateway
error.
Anyway, it’s going to be used only locally, correct?
yes that’s correct. But I still want to use self signed certificate just for extra security and get to know how to successfully configure it.
I’m not sure tesseract supports latex, could you drop a link here?
thanks for explaining
lol. thanks a lot!
I don’t really plan on going total anonymous as I don’t have any bitcoin, it’s just that I don’t want cloudflare, a company to have access to my name and address without having to go through some Legal procedures. The domain is going to associate with my real ip anyway. For me it is good enough that my name is not in whois database or go public
and thanks a lot for providing these info. I guess I’m just going to put in false info and argue that is typo in the future. The most I’m gonna loss is 80$
thanks a lot!
That means everyone could use whois to look up the name and address associated with a certain domain if no privacy protection is provided by the provider right?
good to know!
thanks a lot for sharing the experience!
thanks a lot