Closed vpatel9202 closed 2 years ago
Autoscan does not use Authelia, and also does not show anything on the https://autoscan.domain.tld endpoint unless you also add /triggers/manual
Right, I guess I should have mentioned that but I have a manual trigger set up. Also, regardless of whether or not it shows a web UI, the fact that the URLs are not resolving means that none of the Arr apps can talk to autoscan via webhook, so autoscan can't function at all.
My point is that curl -s --head --request GET autoscan.my.tld
will never do anything as the manual trigger endpoint is the only page it'll ever show you.
Example being
curl -s --head --request GET https://autoscan.domain.tld
HTTP/2 404
content-type: text/plain; charset=utf-8
date: Sat, 09 Apr 2022 10:01:10 GMT
request-id: c98lipnf2ncm9e4n5is0
vary: Accept-Encoding
x-content-type-options: nosniff
x-robots-tag: none,noarchive,nosnippet,notranslate,noimageindex
x-xss-protection: 1; mode=block
content-length: 19
curl -s --head --request GET https://autoscan.domain.tld/triggers/manual
HTTP/2 401
date: Sat, 09 Apr 2022 10:01:18 GMT
request-id: c98lirnf2ncm9e4n5isg
vary: Accept-Encoding
www-authenticate: Basic realm="Autoscan 1.x"
x-content-type-options: nosniff
x-robots-tag: none,noarchive,nosnippet,notranslate,noimageindex
x-xss-protection: 1; mode=block
content-length: 0
Describe the bug When using Authelia (and perhaps without Authelia, not sure), autoscan is not available to any service locally or via external URL. For example, attempting to go to
https://autoscan.my.tld
results in a 404 error page. Attempting to accesshttps://autoscan.my.tld
andhttp://autoscan:3030
from inside an *Arr container also results in a 404 error.I double checked this by running
curl -s --head --request GET autoscan:3030
andcurl -s --head --request GET autoscan.my.tld
from inside multiple containers but the result is always the same:I double checked and the container is on the correct docker network (saltbox) so I don't understand what would stop it from being accessible, at least locally. Traefik shouldn't even enter the picture with inter-container communication. I also tried restarting the autoscan container without authorization enabled but no luck. I don't think that should matter either as it should still return a 401 code rather than 303.
Expected behavior Compare the above with the result when trying to access another container, say Plex (
curl -s --head --request GET plex:32400
):The autoscan container is basically invisible to outside of its own container which means there is no way for *Arr suite to send requests.
Logs Log looks fine: