Hello,

Please attach any screenshots of the error, unfortunately I don't quite grasp the issue you are experiencing as I am unable to reproduce any issues while publishing templates.

Best,
Brody

I created a template, when I click on "Publish Template", nothing happens. No error message. The spinner on the "Publish Template" button spins for a couple of seconds and then stops. (Attached image)

Looking at the request sent, it says 403 error indicating that there could be a permissions issue for my account (Attached image)

When I click on "Publish Template" and it fails, there is no error message shown here, but when i quickly close the template drawer, I can see a "Failed to Fetch" message behind it. (Screenshot attached)

Regarding this, may I know if this is because I need to be a subscriber to publish templates? If that is the issue, is it possible to communicate this specific error message while saving the template.

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Hello,

Thank you for the additional information, I have attached a ticket so we can aggregate reports of this error from other users.

Best,
Brody

Thank you for creating the ticket

Hi all, I was also experiencing the same issue here.

After some investigation, it seems that the input.readme variable (Template Overview field) is prone to being blocked by Cloudflare's WAF.

As an example, entering this line:

3. Select 80(apache2) from the dropdown or manually enter 80

results in the 403 Forbidden response, likely due to the "Select...from" pattern.

The browser Response tab is empty, but copying the request as cURL and running it in terminal shows the Cloudflare error:

This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.

The Ray ID for that particular request was 9591ffedbee1d46c.

Re-wording the line seemed to work, and the template was published successfully:

3. Select the port in the dropdown, or manually enter 80

There were also some CORS errors in the console while receiving the 403s, but it seems they are mostly red herrings.