@ravenet said in Kubernetes management:
For managing your kubernetes, I'd look closely at installing Rancher
Thank you. I'll take a look
@ravenet said in Kubernetes management:
For managing your kubernetes, I'd look closely at installing Rancher
Thank you. I'll take a look
@ronan-a said in XOSTOR hyperconvergence preview:
I just repaired your pool, there was a small error in the conf that I gave in my previous post.
Thank you very much. I really appreciate you fixing this for me
@olivierlambert Thank for for the link.. I obviously still a lot more reading to do:)
@olivierlambert said in Login detail fro Debian 10 cloud-init:
Try to remove and recreate it,
That worked I didn't removed the the hostname in the end.
I can now ssh to the Newly created VM.
No Idea how that's happened
Thank you @olivierlambert
@olivierlambert you guys are doing a great job thank you. I can't wait to see the update next week
@lawrencesystems said in S3 Remote:
I was hoping to avoid this method as my pfsense is not connected at 10G. Thank you for the clarification.
Happy I could help.
@florent said in Unable to connect to backblaze b2:
could you try to connect with the cli aws
I can try, can you please point me to some documentation? I've never done that before
Here is the latest error when saving my settings
remote.test
{
"id": "5c043aa8-8a08-4dcd-bbfb-c2aa214c34d5"
}
{
"name": "AccessDenied",
"$fault": "client",
"$metadata": {
"httpStatusCode": 403,
"requestId": "3d7883ea3ba87dc5",
"extendedRequestId": "aYwU3EzAZOX84u2YJYrNlIWYMMqgz7zNU",
"attempts": 1,
"totalRetryDelay": 0
},
"Code": "AccessDenied",
"message": "not entitled",
"stack": "AccessDenied: not entitled
at throwDefaultError (/opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:8:22)
at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:18:39
at de_GetObjectLockConfigurationCommandError (/opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/client-s3/dist-cjs/protocols/Aws_restXml.js:4476:12)
at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@smithy/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24
at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/middleware-signing/dist-cjs/awsAuthMiddleware.js:14:20
at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@smithy/middleware-retry/dist-cjs/retryMiddleware.js:27:46
at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/region-redirect-endpoint-middleware.js:14:24
at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/region-redirect-middleware.js:9:20
at /opt/xo/xo-builds/xen-orchestra-202311151203/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:7:26
at S3Handler._sync (/opt/xo/xo-builds/xen-orchestra-202311151203/@xen-orchestra/fs/src/s3.js:452:19)"
}
@olivierlambert said in Unable to connect to backblaze b2:
Have you asked Backblaze first?
After 9 days of back and forth, I am now back to my starting point...
Backblaze is saying that there is no problem at their end so check xcp-ng...
I just woke up one morning to see that the remote was no longer working.. It has been working perfectly for almost a year... I updated Xen Orchestra community in case it was a bug but I am still not able to connect...
I am running Xen Orchestra, commit af7aa with Master, commit 03de8
Could anyone please help me?
Thank you
@olivierlambert said in Unable to connect to backblaze b2:
Have you asked Backblaze first?
No but I will.
Hi,
I logged a forum entry saying that I wasn't able to restore from backup and it was pointed to me that my backup remote was offline.
I tried to recoonect my Backblaze S3 remote and I keep getting this error message:
remote.test
{
"id": "5c043aa8-8a08-4dcd-bbfb-c2aa214c34d5"
}
{
"name": "AccessDenied",
"$fault": "client",
"$metadata": {
"httpStatusCode": 403,
"requestId": "c6fc8c7e4f7a82ab",
"extendedRequestId": "aYyE3pDBGOcM4fGauYlRl+GaiMpQz5TPd",
"attempts": 1,
"totalRetryDelay": 0
},
"Code": "AccessDenied",
"message": "not entitled",
"stack": "AccessDenied: not entitled
at throwDefaultError (/opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:8:22)
at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:18:39
at de_GetObjectLockConfigurationCommandError (/opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/client-s3/dist-cjs/protocols/Aws_restXml.js:4476:12)
at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@smithy/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24
at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/middleware-signing/dist-cjs/awsAuthMiddleware.js:14:20
at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@smithy/middleware-retry/dist-cjs/retryMiddleware.js:27:46
at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/region-redirect-endpoint-middleware.js:14:24
at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/region-redirect-middleware.js:9:20
at /opt/xo/xo-builds/xen-orchestra-202311071630/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:7:26
at S3Handler._sync (/opt/xo/xo-builds/xen-orchestra-202311071630/@xen-orchestra/fs/src/s3.js:452:19)"
}
I know for sure that the credental are correct but in doubt, I then created a new API credential and even with that the detrails, I keep getting the same message: "not entitled"
I am running Xen Orchestra community Xen Orchestra, commit 9dea5
Master, commit 9dea5
Could anyone please assist me ?
Thank you
@olivierlambert said in No back available to restore:
Then make sure your backup repository is correctly connected.
Bingo. All my backblaze credential seem to have disappeared
@olivierlambert said in No back available to restore:
Click on "Refresh backup list".
I did that and nothing happened
Hi,
I have set a Delta backup a while ago and just realised that the last few weeks backup failed when trying to restore a VM. I decided to go to the last successful back as per screenshot bellow but the backup doesn't appear in the backup list
Could anyone please help me understand why my backups are not showing the the restore tab?
Thank you
Hi,
I found an old blog post saying that we can add/remove our ssh key in the user area but I cannot see this option on my screen. Could anyone please tell me where to go to delete existing keys from Xen Orchestra?
Thank you
Fred