[SOLVED] Error: Request failed with status code 403, moralis-admin-cli

Moralis General
#1

moralis-admin-cli watch-cloud-folder get-logs
Error: Request failed with status code 403

moralis-admin-cli watch-cloud-folder --moralisApiKey *** --moralisApiSecret *** --moralisSubdomain **.usemoralis.com 
--autoSave 1 --moralisCloudfolder D:\..\moralis-cloud-func\cloud
...
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Request failed with status code 403

The CLI API Key and CLI API Secret parameters are copied ,Canā€™t go wrong

It was normal the other day

#2

Update and restart have been tried

We still get an error 403

#3

Did you try with another server too?

#4

I just created a new server

Itā€™s the same problem

These two parameters are the same input for the same account
--moralisApiKey --moralisApiSecret

Only subdomains are different
--moralisSubdomain

#5

you can try to regenerate them in admin interface, with regenerate all secrets

#6

Regenerate all secrets also tries

There is no effect

But itā€™s back to normal today. Strange??

The parameters donā€™t change at all

#7

yes, strange, you didnā€™t change the parameters after resetting all secrets? as in, it works with old parameters?

#8

It will be implemented on April 20

Regenerate all secrets also tries

There is no effect

We still get an error 403

But try again on April 21st and it will work

#9

it works fine now? just to make sure that the problem was fixed somehow

#10

Yes, itā€™s normal now

1 Like
#11

this is happening to me now, i canā€™t sync cloud folder :frowning: same errorā€¦ i donā€™t see any clues here about the root cause :((( )

#12

is the server working fine? it worked before with same command?

you can still use legacy.moralis.io and edit the cloud code directly there

#13

same issue here and it also happens with ā€œconnect-local-devchainā€ option even when the connection works with raw FRPC binary.

This is a brand new server with just 3 days, and I also try regenerating all the secrets with same behavior

NEXT_PUBLIC_APP_ID=GXWqEgDRYAb3cJTAlrvZCtHCcwIEXiYMUbtUfXqT
NEXT_PUBLIC_SERVER_URL=https://rmjhzsvwavyk.usemoralis.com:2053/server

#14

If it works with frpc directly then you can use that