-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API service at '10.20.0.1' using the 'http' protocol at /usr/share/perl5/PVE/Storage/LunCmd/FreeNAS.pm line 389. #183
Comments
What version of TrueNAS? |
TrueNAS-12.0-U6.1 Core |
What branch of the plugin are you using...testing or stable? |
I believe I was using stable, but at this point I really cannot remember. |
The 'testing' repo has the Bearer Token auth feature so no more User/Password is needed on newer TrueNAS version. |
Only select "ONE" repo. |
I'm sorry, I'm not really too sure what I should do from here to fix this. |
Click on the "stable" repo and a few button will appear below "APT Repositories". One should be |
I'll be back. Off to my real job for awhile. |
I'm trying to set this up on TrueNAS Scale now instead, most recent stable version. |
Send me that snip of the config in the /etc/pve/storage.cfg and, or course, remove/change |
So the Raid 1 boot drives both failed in this proxmox host last night. Brand new custom server build less than a week old. |
Should be following the instructions at https://github.com/TheGrandWazoo/freenas-proxmox?tab=readme-ov-file#new-install-instructions |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm having this issue above, I'm not sure where to go next, I've been at this for about 25 hours.
If there is anything you need me to provide please let me know.
I also receive this when trying to delete a vm disk
()
Unable to connect to the FreeNAS API service at '10.20.0.1' using the 'http' protocol at /usr/share/perl5/PVE/Storage/LunCmd/FreeNAS.pm line 389. (500)
The text was updated successfully, but these errors were encountered: