starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: IPv6 Unique Local Address Socket Connection Failure #2997

New Issue
Open
opened 2026-04-25 00:12:53 +02:00 by adam · 1 comment
adam commented 2026-04-25 00:12:53 +02:00
Owner
Copy Link
Copy Source

Originally created by @DarkArc on GitHub (Sep 11, 2025).

What happened?

When using an IPv6 based connection e.g., http://[fd12:ac4a:1e71:7fa8:9b99:93ef:3c00:c9e9] the application seems to fail to establish the (web?) socket to update progress.

What did you expect to happen?

Socket connection succeeds without issue

Steps to reproduce the issue

  1. Use an IPv6 ULA (Unique Local Address) connection directly in the URL

Audiobookshelf version

v2.29.0

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Firefox

Logs

Additional Notes

No response

Originally created by @DarkArc on GitHub (Sep 11, 2025). ### What happened? When using an IPv6 based connection e.g., `http://[fd12:ac4a:1e71:7fa8:9b99:93ef:3c00:c9e9]` the application seems to fail to establish the (web?) socket to update progress. ### What did you expect to happen? Socket connection succeeds without issue ### Steps to reproduce the issue 1. Use an IPv6 ULA (Unique Local Address) connection directly in the URL ### Audiobookshelf version v2.29.0 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? Firefox ### Logs ```shell ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:12:53 +02:00
adam commented 2026-04-25 00:12:53 +02:00
Author
Owner
Copy Link
Copy Source

@DarkArc commented on GitHub (Sep 11, 2025):

This seems to resolve by just using an IPv6 DNS record, so it presumably is something with how the host is extracted from the URL to set up the web (?) socket.

I'm also unsure what exactly the socket failure is actually doing ... the console suggests progress sync is failing but in actuality things seem to be syncing fine?

@DarkArc commented on GitHub (Sep 11, 2025): This seems to resolve by just using an IPv6 DNS record, so it presumably is something with how the host is extracted from the URL to set up the web (?) socket. I'm also unsure what exactly the socket failure is actually doing ... the console suggests progress sync is failing but in actuality things seem to be syncing fine?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2997
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?