forked from beam/freenas-proxmox
-
-
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
Proxmox 8.1 and Truenas Core Problem #182
Comments
TrueNAS or TrueSAN? Never heard or TrueSAN. |
TheGrandWazoo
added
Question
Further information is requested
Diagnose
Diagnose/Discuss a issue or concern
labels
Mar 22, 2024
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #181
Originally posted by cundaric March 21, 2024
ello,
I followed step by step the installation instructions but I'm getting the following error when trying to execute qm rescan command on Proxmox 8.1 and Truesan Core
Unable to connect to the FreeNAS API service at '192.168.20.7' using the 'https' protocol at /usr/share/perl5/PVE/Storage/LunCmd/FreeNAS.pm line 380.
Plugin version
pkg -l |grep freenas
ii freenas-proxmox 2.2.0-1 all FreeNAS Plugin for Proxmox VE
line 380 "die "Unable to connect to the FreeNAS API service at '" . $apihost . "' using the '" . $scheme . "' protocol";"
IP is reachable on the port:
curl -k -I https://192.168.20.7/api/
HTTP/2 302
server: nginx
date: Thu, 21 Mar 2024 08:57:51 GMT
content-type: text/html
content-length: 138
location: https://192.168.20.7/ui/
strict-transport-security: max-age=63072000; includeSubDomains; preload
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
permissions-policy: geolocation=(),midi=(),sync-xhr=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()
referrer-policy: strict-origin
x-frame-options: SAMEORIGIN
Any ideass?
The text was updated successfully, but these errors were encountered: