BramSuurdje / proxmox-helper-scripts

Modern front-end for the Proxmox VE Helper Scripts project, built with Next-js, Shadcn, and Pocketbase.
https://proxmoxve-scripts.com/
MIT License
35 stars 5 forks source link

Backend API not resolving, webpage returns no content #8

Closed ALParsons closed 5 months ago

ALParsons commented 5 months ago

Describe the bug When loading the website script library, no scripts are shown and the website is empty. Opening the console shows an "address invalid" error for the backend API request > https://pocketbase-proxmox-helper-scripts.fly.dev/api/collections/categories/records?page=1&perPage=500&skipTotal=1&expand=items

To Reproduce Steps to reproduce the behavior: Load the website and attempt to view the scripts.

Expected behavior Script library should load.

Screenshots image

image

tteck commented 5 months ago

No issue here.

Screenshot 2024-05-13 6 51 25 PM

ALParsons commented 5 months ago

I'm going to lose it if it's my own DNS implementation, let me do more digging.

BramSuurdje commented 5 months ago

is it possible for you to just go to the raw api link in a browser?

https://pocketbase-proxmox-helper-scripts.fly.dev/api/collections/categories/records?page=1&perPage=500&skipTotal=1&expand=items

it should result in a whole lot of json

ALParsons commented 5 months ago

Sorry I dropped off for a bit, wife's birthday.

I quickly found that it's being filtered out by my controld "AI Malware" filter. I will create an exception for it but maybe a CNAME record or other API endpoint domain to replace the current endpoint could also resolve the issue. "fly.dev" may not have a good reputation.

image

ALParsons commented 5 months ago

allowlist exception in place now:

image

tteck commented 5 months ago

Usage Warning

This feature is experimental and may cause false positive blocks for less popular websites, on uncommon TLDs. Use at own risk.

The above is from their documentation at https://docs.controld.com/docs/ai-malware-filter

I don't think the issue is with fly.io reputation.

ALParsons commented 5 months ago

Sure, it is an uncommon TLD (fly.dev). I have implemented a bypass rule, and it resolves as expected. The issue can happily be closed as-is, or feedback integrated (to migrate the API's DNS endpoint so that it is not on a lesser known TLD).

Cheers