500 Server Error if Proxmox datastore is not configured on selected node

[CreeperFace00]

Describe the issue

I have been struggling with an issue with the Proxmox service where if a storage dataset is not configured on the selected node in the service tab, I will get a 500 server error when trying to configure a package.
It is possible to get around this by sharing all datasets across each node via NFS and enabling via cluster management, however this is not possible for things like ZFS pools configured through the Proxmox web ui.

Product Version

2.2.1

Pterodactyl Panel Version (if applicable)

No response

To Reproduce

1. Configure the Proxmox service
2. Create a new package
3. Click Service
4. Select a node with a dataset that is not shared
5. In storage, select a dataset that node is not configured for or a ZFS pool on a different node
6. See that the page now returns the 500 error and the Service (Proxmox) tab can no longer be accessed

Expected Behaviour

Ideally when selecting a node, only datasets that that node is configured to access should appear in the storage dropdown.
Alternatively as a simple workaround, make it so that the package does not become softlocked with the 500 error if you select a dataset the selected node is not configured for.

Screenshots

Additional Information

No response

[EWANZO101]

Hello unfortunately the proxmox service is no longer being working on but you can go to the bottom of the wemx docs where proxmox is u will find a link to a manual way of doing a proxmox vm