-
-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
teslalogger.de returning http 408 #787
Labels
bug
Something isn't working
Comments
I aware of this problem. My webhoster is not able to handle requests from almost 3000 Teslalogger. I'm about to setup a new root server. |
Thanks for the quick response. I guess it does not make sense to try the ScanMyTesla integration until that is done... |
teslalogger.de is now on a root server. |
"This is a problem you can throw money on"
seriously: another sponsoring round required?
Am 24.04.2022 um 20:34 schrieb Christian P.:
…
I aware of this problem. My webhoster is not able to handle requests
from almost 3000 Teslalogger. I'm about to setup a new root server.
—
Reply to this email directly, view it on GitHub
<#787 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AL4L3BGFHWFAZ3RVY3UBUU3VGWH3VANCNFSM5UFYBASQ>.
You are receiving this because you are subscribed to this
thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Anyone else having issues with teslalogger.de website returning HTTP error 408 (Resource Limit Is Reached)? It seems to be affecting also the functionality of my docker instance of TeslaLogger (which also shows http 408 errors in its logfile). I tried accessing the website from multiple locations and I think it started already on Friday...
The text was updated successfully, but these errors were encountered: