[Bug]: 2.8.1 (Docker) Library Scan Fails Getting Repeated "alert number 12" in log file

[freddyyeddy]

Describe the issue

When triggering library scan (using NFS so I cant trust auto scans) It throws The Errors Below. Im gonna let it take forever and see if it finally finishes and detects the one New audiobook. After Looking at Debug log it looks like more work than dont (Second Image). So I suspect this could be a red herring.

Steps to reproduce the issue

1. Manually Trigger Library Scan And Watch.

Audiobookshelf version

1.8.2

How are you running audiobookshelf?

Docker

[freddyyeddy]

Update With It finished (First Image) and picked up the new Book. But it seems needlessly long for a simple single book find. Has there been a change to the scan methodology that affects if pre-existing books are re-checked after updating. The second scan seems more reasonable (Second Image). So I assume It has to do with how the update process (re-pull/build container for latest version). If Im right might be worth updating the Change notes for clarity. Im closing this ticket myself as seems problem did not persist.

[freddyyeddy]

I seems this is still happening and I can no longer search Audible For Meta data either. I added another batch of audiobooks and the search seemed to do a full scan and take forever and threw the alert 112's

[nichwall]

Looks like TLS error 112 is something specific to your setup, or an issue with Audnexus?

https://stackoverflow.com/questions/5671000/what-does-this-tls-alert-mean

[freddyyeddy]

I cant Seem to find any real reason for this to happen. All I did was update docker image to new version. Then it started happening. Got any tips for where to look. I basically turned off the firewall for the server. So I dont think its bocking there. I recently moved to using ngix proxy manager. But the reverse proxy has been fine there too. This happens when I attempt to search for a match.

[advplyr]

Are you getting this error using a local ip address?

[freddyyeddy]

No I'm using a DNS to access the instance via reverse proxy (web socket enabled).

[freddyyeddy]

Checking Via Local IP:Port and still same same (Searched different book this time)

[github-actions]

After reviewing this issue, this appears to be a problem with your setup and not Audiobookshelf. This issue is being closed to keep the issue tracker focused on Audiobookshelf itself. Please reach out on the Audiobookshelf Discord for community support.
Some common search terms to help you find the solution to your problem:

• Reverse proxy
• Enabling websockets
• SSL (https vs http)
• Configuring a static IP
• localhost versus IP address
• hairpin NAT
• VPN
• firewall ports
• public versus private network
• bridge versus host mode
• Docker networking
• DNS (such as EAI_AGAIN errors)

After you have followed these steps, please post the solution or steps you followed to fix the problem to help others in the future, or show that it is a problem with Audiobookshelf so we can reopen the issue.

[freddyyeddy]

No problem. I am unsure what directly was causing the issue but Its been resolved. Thanks for the help and support. Sorry I left this go stale and never followed up.

…

On Wed, Sep 11, 2024, 5:45 AM github-actions[bot] ***@***.***> wrote: After reviewing this issue, this appears to be a problem with your setup and not Audiobookshelf. This issue is being closed to keep the issue tracker focused on Audiobookshelf itself. Please reach out on the Audiobookshelf Discord for community support. Some common search terms to help you find the solution to your problem: - Reverse proxy - Enabling websockets - SSL (https vs http) - Configuring a static IP - localhost versus IP address - hairpin NAT - VPN - firewall ports - public versus private network - bridge versus host mode - Docker networking - DNS (such as EAI_AGAIN errors) After you have followed these steps, please post the solution or steps you followed to fix the problem to help others in the future, or show that it is a problem with Audiobookshelf so we can reopen the issue. — Reply to this email directly, view it on GitHub <#2782 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGIXG6YSXWB7YEKERQO7ZVTZWBCOVAVCNFSM6AAAAABFCSELBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBTG4ZDAMZSGA> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>