-
Notifications
You must be signed in to change notification settings - Fork 1
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
Error: failed to get policy: failed to get OK status code: 401 Unauthorized #15
Comments
Hi, @plittlefield , thanks for opening an issue ! EDIT: I have updated the README to add clearer setup instructions, don't hesitate to check it out. |
Thanks, I will redo it all and read the new setup instructions and try again :) |
OK, so I have tried again and get to the same point after reading your new setup instructions. I have connected my laptop to my tailnet, can tailnet ip and tailnet ping to check that part works. I have an AWS account, have the AWS cli installed and can list my other running instances to check that part works. I have installed tailout. I have created a tailout config file, my headscale server has created an API which I have added to check that part works. However ... If I run tailout init, I get this error ...
If I run tailout create, this is the (sanitised) output ...
What am I doing wrong? Are there any verbose logs I can check? Thanks. |
Thanks for giving it time. I think the problem comes from using Headscale. Tailout only queries the Tailscale API and I haven't tested it with Headscale. |
Nice! Thanks and keep up the great work. |
I just pushed the feature, you can try by updating to v0.3.2 : |
Thanks! I’ll try tomorrow and report back! |
Hi, Well, a bit further I think ...
Here is my (sanitised) config ...
Happy to try some beta version to fix this. Here is the page on my Wiki for Headscale ... https://wiki.indie-it.com/wiki/Tailscale Thanks. |
Hey thanks for reporting back, I've been able to reproduce your issue using a Headscale instance I just set up.
I'll try to find a workaround! |
Reporting back, it appears that the tailscale client SDK hardcodes all the routes it uses for the calls, see the faulty call for example : https://github.com/tailscale/tailscale-client-go/blob/main/tailscale/client.go#L501. |
Oh, so … for the time being it’s a non starter for me. Is there anything the developer of Headscale can do to help? |
I’ve opened a feature request issue :) |
Awesome, thanks for pushing for this! |
I'm sure I have missed something in your instructions.
When I run
tailout init
I get the error:-
Error: failed to get policy: failed to get OK status code: 401 Unauthorized
I have an AWS_PROFILE environment variable set with correct permissions for EC2.
The text was updated successfully, but these errors were encountered: