StatusCode: 403, Type: authorization_required, APIMessage: Not allowed

[dimaspencer84]

Hey !
I set the public key, the access key and the generated token properly, but I still get these errors...How can I fix it ?
2 error(s) occurred:

* scaleway_server.machine[1]: 1 error(s) occurred:

* scaleway_server.machine.1: StatusCode: 403, Type: authorization_required, APIMessage: Not allowed
* scaleway_server.machine[0]: 1 error(s) occurred:

* scaleway_server.machine.0: StatusCode: 403, Type: authorization_required, APIMessage: Not allowed`

[dimaspencer84]

I found where the problem was coming from. ;-)

[Vad1mo]

Glad you found the solution. Can you share it so other in the same situation can benifit and are encouraged to contribute as well.

Btw. Don't forget to 🌟 our project if you like it or send improvements.

[dimaspencer84]

I successfully created a workshop using your tool but the script ended with a error message:

scaleway_server.machine[0] (remote-exec): ...installing docker-compose done. Installed Version is 
docker-compose version 1.15.0, build e12f3b9
scaleway_server.machine[0] (remote-exec): Granting user ubuntu Docker daemon access
scaleway_server.machine[0] (remote-exec): adduser: The user `ubuntu' does not exist.

Error: Error applying plan:

2 error(s) occurred:

* scaleway_server.machine[1]: 1 error(s) occurred:

* Script exited with non-zero exit status: 1
* scaleway_server.machine[0]: 1 error(s) occurred:

* Script exited with non-zero exit status: 1

So the command adduser doesn't get executed...
Moreover when I access the machine remotely via rdp (using the root user), some commands (including adduser) are not available and it's impossible to create files/folders within the "thinclient_drives"...

[Vad1mo]

I see the error is here:

Cloud-Workshop-VM/files/docker.sh

Line 27 in 90abb64

adduser ubuntu docker

the user ubuntu isn't there on SCW but on AWS, you should remove the line on SCW.

[Vad1mo]

I did an update this should work now on SCW again.