I noticed that there's 33% health with the template.

Not sure what's wrong with it. If anyone having the issue let me know.

Currently, there are 2 failed deploys, they have failed with a 401 unauthorized error.

Looks like it was no fault of your template.

I see, most likely this is issue with our API key maybe they did not configure their client ID to allow Railway domain.

Not sure, not much more I can say on the topic.

Yeah, I have to replicate the issue to improve the health rate at least.

take a look at this case https://help.railway.com/questions/there-is-an-error-rpc-request-failed-wi-cf5f0d75

Let me check this for you.

Responded, API key issues. Please configure your allowlist.

Brody, what domain is being use when deploying the template? I tried *.up.railway.app still does not work.

It would be random for every deployment.

is there no other domain being use here? I tried everything. railway.app, railway.com still no luck.

This feels more like an XY problem, what are you trying to achieve?

I'm doing a test for the template to ensure it will have 100% health and ensure it will work as they deploy it.

Here's the error, this is more of our issue, to allow domain but don't know which domain to allow.

I don't want to allow all domain to make this work. Maybe the deploy uses a different domain.

After I allow all the domain it works, so I want to know which domain to be in the allowlist to ensure it will work for users with restricted access.

Where does the allowlist live?

On our dashboard here's the example:

You can actually try to replicate by signing up and then create a new project.

https://thirdweb.com

Then the user is going to have to copy their randomly generated domain into that box.

Got it thanks Brody, just created the tutorial here: https://support.thirdweb.com/general-thirdweb-issues/vGcHXQ7tHXuSJf7jaL2y5Q/how-to-deploy-nft-drop-template-to-railway/4h2eJs1HENrv1tzWRXS89Z