mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-05-04 18:08:46 +03:00
An unknown error occurred when the SMTP host could not be reached #4943
Closed
opened 2026-02-05 09:28:15 +03:00 by OVERLORD
·
9 comments
No Branch/Tag Specified
development
l10n_development
release
v26-03
ci_fixing
codeberg-actions
lexical_may_2026
MilnerMart/development
sort_rule_text
GamerClassN7/impersonations-for-admin
Zhey-on/feature/csp-image-css-controls-6033
tortillas5/development
clauvaldez/mfaReset
llm_only
vectors
McTom234/oidc-key-algorithms
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v26.03.4
v26.03.3
v26.03.2
v26.03.1
v26.03
v25.12.9
v25.12.8
v25.12.7
v25.12.6
v25.12.5
v25.12.4
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#4943
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @mschoon85 on GitHub (Sep 6, 2024).
Describe the Bug
Hi @ssddanbrown,
I've opted to submit a separate bug report since the same issue has arisen on both our former Bookstack server (Windows) and our current one (Linux). Errors occur when creating new pages in specific books; the pages are created, but the error remains. This issue can be replicated by changing the MAIL_HOST in the .env file to a non-existent address. It's important to note that not all books are affected by this issue. Moreover, I encounter this error even when I'm not subscribed to the book anymore. Whenever I revert the MAIL_HOST to a valid address, the problems disappear. It's probable that the issue would recur if the MAIL_HOST were unreachable at the moment of saving the page.
Please inform me if you require any information from the server logs or similar resources.
Kind regards,
Michel
Steps to Reproduce
Note: The new settings with the non-existent mail host were only applied after executing php artisan config:cache. The reason for this is unclear.
Expected Behaviour
One would expect emails to accumulate in a queue until the mail host becomes available once more.
Screenshots or Additional Context
Browser Details
Edge
Exact BookStack Version
24.05.3
@mschoon85 commented on GitHub (Sep 6, 2024):
When I enable debug mode:
Symfony\Component\Mailer\Exception\TransportException
Connection could not be established with host "smtp.xxx1:25": stream_socket_client(): php_network_getaddresses: getaddrinfo for smtp.xxx1 failed: No such host is known.
PHP Version: 8.3.7
BookStack Version: v24.05.3
Theme Configured: custom
Details
@ssddanbrown commented on GitHub (Sep 7, 2024):
There is no queue unless you specifically enable it, which will also require a queue worker as described in our documentation:
https://www.bookstackapp.com/docs/admin/email-webhooks/#async-action-handling
Otherwise, errors will be thrown as experienced if the system is trying to mail but encounters errors.
@mschoon85 commented on GitHub (Sep 10, 2024):
By adding QUEUE_CONNECTION=database to the .env file, the error is resolved. Emails should now be stored in the database if I'm not mistaken. I will look for a method to continuously run the Queue Worker Process in the Docker container once I have a functioning external SMTP server, as opposed to using our internal server.
Thanks @ssddanbrown !
@pnunn commented on GitHub (Sep 19, 2024):
I just spent about an hour chasing this one down too when trying to add a new user. I had send the invitation checked, and because no smtp server is configured in the docker container its running in, I got unknown error. A better error message would be greatly appreciated because I was looking for errors to do with adding users, not email errors.
@ssddanbrown commented on GitHub (Sep 19, 2024):
@pnunn Yeah, I agree, this is likely to be the first use of email for many so adding extra specific handling for email errors for better guidance would probably be worthwhile here.
I'll update & recategorise this issue to be focused on improving the error flow here.
@ssddanbrown commented on GitHub (Sep 29, 2024):
Specific handling with error display (while returning the user back to the form with previous form input) has now been added via
d12e8ec923, which will be part of the next feature release.Thanks @mschoon85 and @pnunn for your input.
@mschoon85 commented on GitHub (Oct 14, 2024):
Hi @ssddanbrown,
I have updated to BookStack v24.10, but I still encounter the error 'An unknown error occurred' whenever QUEUE_CONNECTION=database is not enabled and an invalid or unreachable SMTP server is set in the .env file.
Interestingly, not all books seem to be affected. New books and some existing books do not trigger this error. I’m wondering if this issue might be related to the books I follow or have followed in the past.
Kind regards,
Michel
@ssddanbrown commented on GitHub (Oct 14, 2024):
Yeah, the update changed nothing in that regard, just added better handling for the user invite flow since that's a common first encounter for email sending.
Generally I'd expect it to be watches from other users, since notifications should not be sent for your own actions, but you can see the content you're watching from your notification preferences area in "My Account", otherwise you could peek into the
watchestable of the DB to quickly see if there are any watches across all users in general, although there's also notification preferences.@mschoon85 commented on GitHub (Oct 21, 2024):
@ssddanbrown, I have cleared all rows from the watches table in the test environment, but I cannot do this in production. The unknown error has now disappeared, confirming that it was caused by watches from other users. However, this still points to a deeper underlying issue: an incorrect SMTP configuration, an SMTP address that does not exist, or one that is unreachable. Would it be reasonable to create a fix to prevent users from receiving the unknown error message?