-
Notifications
You must be signed in to change notification settings - Fork 14
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
Fallback not being used with SSL timeouts #85
Comments
👋 This is us! We're seeing this with our Broadcaster for Laravel package that extends ably-php https://github.com/springboardVR/Laravel-Ably-Broadcaster It looks like it mostly is happening when we're doing |
To clarify, the task here to to check whether or not that error is triggering a fallback to be used. It should be, but the fact that a customer is seeing the error is evidence that it might not be (as it's unlikely that all fallbacks tried would all give an ssl timeout), so we don't currently know whether it is or not. |
There're a number of unit tests regarding fallback hosts, for instance: That error can only be produced in https://github.com/ably/ably-php/blob/master/src/Http.php#L161 With log level set to error you should see a message for every failed attempt. The default is warning, so you should see them. By default fallbacks will be used, you can verify the list of fallback hosts with: $ably = new AblyRest( $opts );
print_r( $ably->options->fallbackHosts ); |
@matthewhall-ca any chance you can share some of the logs when this happens? |
It hasn't happened in a while! Will let you know when it does |
Improve error logging via #119 |
We've had a report from a customer that when publishing, they'll sometimes see
Ably\Exceptions\AblyRequestException cURL error: SSL connection timeout
and try to use the fallback host.The text was updated successfully, but these errors were encountered: