-
Notifications
You must be signed in to change notification settings - Fork 13
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
scytale init error message with "Server closed" #350
Comments
From the quick scan of your ticket, sounds like tr1d1um doesn't like the scytale endpoint it was provided. Try curling your scytale server ports to make sure your scytale server is working as expected. |
@denopink Hi, thanks for info. After I set targetURL to "targetURL: http://localhost:6300/api/v3", the error message got different with tr1d1um launch. (503 Service Unavailable) curl command request and result,
|
The 503 is expected since that's scytale trying to reach out to a local talaria on port looks like your scytale server is working as expected 🙂 if you have any questions regarding talaria, then feel free to create a new ticket in talaria otherwise I'm closing this ticket |
@denopink sorry for disturb, do you know about my new issue with case xmidt-org/tr1d1um#498? |
yup, it's on my queue. |
Somebody can help with this issue?
I launched the scytale, but it showed some "Server closed" messages, wondering if it got some error?
I send curl command to tr1d1um (curl -H 'Authorization: Basic dXNlcjpwYXNz' -i http://localhost:6100/api/v2/device/mac:112233445566/stat), but it showed "400 Bad Request", not sure if it is related with tr1d1um or scytale error.
The text was updated successfully, but these errors were encountered: