`502 Bad Gateway` Does anyone know what could be w...
# suitescript
j
502 Bad Gateway
Does anyone know what could be wrong? I am using suitescript 2.0 RESTlet to get a record, can make a successful call in my instance, but when I move the script to customer instance, I get this error, the script is the same.
b
might want to see if there is a more helpful message in the body
but general debugging steps is to make sure that you are using the correct url found on the script deployment
and that the script deployment's status is released and the script audience correctly
importantly you want the script audience to include the user/role you are using for authorization
you also should switch to tba if you are using the user credentials through the nlauth authorization header
j
@battk is it make sense to select all audience? yeah i am using token based authentication
b
if you are trying to follow best practices, you would limit the script audience to only the users/role that need access to your restlet
👍 1
if you are trying to fix an error, i would simple recommend setting all roles
j
fixed,
502
error because we deployed the script in sandbox, but customer connect to the production. Thanks @battk