Getting error regarding access token for Custom Component Library on "dev", not on "login"

💬 App Building
1
  1. My goal:
    Deploy a custom component
  2. Issue:
    Getting the following error after running npx retool-ccl deploy:
    Error creating new version of custom component library: Access token is not valid or does not have custom component permissions.

We have confirmed the scopes of the token; this used to happen on login prior to fixing that issue, but it's happening on dev or deploy now when Sending updated code to retool...

The Custom Component Library gets created, just not the components.
3) Steps I've taken to troubleshoot:

  • Confirmed scopes
  • Called the API with the access token to GET libraries and noticed my library was indeed there.
  1. Additional info:
    Self-hosted
    Retool version: 3.148.5
    retool-ccl version: 1.7.4

I have reached out to our DevOps team which manages the instance for additional logs, but any guidance on how to instruct them to do so or on how to enable more verbose logging from retool-ccl would be very appreciated! I have looked through similar posts, but they seem to all have occurred on retool-ccl login and not when sending the updated code.

Thank you!

2

Update: this may be an issue with Cloudflare. I called our self-hosted Retool's API directly with the files and received a 403 Forbidden with a response from Cloudflare.

image
image1059×474 38.3 KB

(and more detailed information specifically from Cloudflare follows)

I figured that using the API, I'd get more detailed information than from the CLI tool, so using Create a new custom component library revision, I was able to get the 403 Forbidden.

Once I get past the Cloudflare issue, I will update if that fixes the issue, but I figured this information might be helpful if others run into the same issue in the future. It might be good to update that CLI tool to have a more descriptive error message or to display the status code if this is the case.

1 Like
3

Welcome to the community, @mblumenshine! Thanks for reaching out and for providing an update to your original post, as well. Let us know if you learn anything helpful from the DevOps team about potential Cloudflare configuration issues. Should that prove unsuccessful, there are some other lower-level things we can try. :+1:

1 Like
4

Thanks for your response!

We got past Cloudflare but received a 500 internal server error when trying from Postman. It's possible that my API request was malformed. Though even so, we still get the original error with the actual CLI tool.

Sadly, we're reprioritizing and have an alternative solution to get enough functionality to be viable, so likely won't continue investigating this. However, a custom compoonent would be ideal and I asked our DevOps team for additional insight into our Retool instance and logs with the hope that they'll turn up something I can act on or provide here.

Thank you!

1 Like
5

Sounds good! I'll leave this topic open for when you want to return to the project. :+1: