Hi there mate! A Happy New Year to you too and all the XCP-ng family!

@Mark-C

Wouldn't have made it without your help! Super.

So far everything seems to be working normally, except for my original issue on the other topic, posting there now.

If any more issues come up I'll post them here and reference on this topic. Many thanks!!

@julien-f so i should issue yarn build after doing npm i gotcha. Give me a couple minutes will update you in an instant.

@julien-f Hi Julien I haven't, but I will do it and let you know the results. I've already started another XO instance non-ARM until this one gets working again, let me know if you'd like me to wipe it clean and install from scratch.
Will do the --legacy-peer-deps and --force afterwards depending on outcome

the export had the wrong anonuid and anongid bc I was taking the uid and gid from an outdated document. I felt really stupid........

Seen this too late today but I will give it a whirl tomorrow! Will let know how it went.

Oh ok. I will replace the Center schedule and re-do it here in XO. Thank you so much!

Hi @tony yes I understand that, actually I made a post a while back spanning different aspects of the XOA and where I feel Center is more intuitive but as suggestion for XOA improvement if anyone cares to consider it.

Regarding the adding of SR's to pools, I leave my suggestion here, have a selector for pool instead of host, it'd be more intuitive imho. Cheers all.

@julien-f as I posted on the other ticket, yarn failed and left xo-orchestra unrecoverable. I'm not looking to break any forum policy nor made any aggressive comment, I am clearly stating that pushing a feature on an application that worked on any instruction set, only to make it incompatible with a whole family of systems, is a bad approach.
However, this is expressing a honest opinion is not an aggression. And yes, I posted a solution suggestion, as I always do, if possible I try to help. I'm not a developer, can't integrate solutions cause that's not my expertise, but certainly have no issue in doing research and trying to bring something to the table.
And since we're on that topic, I would also suggest you guys to take a look into Oracle Cloud Infrastructure, as they have an "always free" tier which includes computing instances, if you use ARM it gives you up to 6 CPU and 18GB RAM on that free tier. I believe it will be useful. Thank you.

Edit:
I added the suggested line to packages/xo-server/config.toml. Yarn fails just the same.

It's great, specially because it broke XO for those using ARM instances. Good job.

just a personal opinion I'm leaving here, no follow-up needed.

If I want to run containers I use OKD.
I've always seen all the comments about keeping the dom0 controller to a minimum, docker alone adds a 2GB overhead to it, no more problems in adding stuff to it.

@pdonias ok I get a correct answer from inside but from outside I'm getting this bad request. The curl gets to the ssl certificate on the net box host, but throws the 400 bad request, when doing from outside the firewall.

When testing locally, it works.

Let me look this over! Thanks!

@pdonias

Just to say that yes the link is accessible.

HTTP 200 OK
Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 1,
    "next": null,
    "previous": null,
    "results": [
        {
            "id": 1,
            "url": "https://fw-dea12.domain.tld/api/extras/custom-fields/1/",
            "display": "UUID",
            "content_types": [
                "virtualization.cluster",
                "virtualization.virtualmachine",
                "virtualization.vminterface"
            ],
            "type": {
                "value": "longtext",
                "label": "Text (long)"
            },
            "object_type": null,
            "data_type": "string",
            "name": "uuid",
            "label": "UUID",
            "group_name": "",
            "description": "Object UUID",
            "required": false,
            "search_weight": 1000,
            "filter_logic": {
                "value": "exact",
                "label": "Exact"
            },
            "ui_visibility": {
                "value": "read-write",
                "label": "Read/Write"
            },
            "default": null,
            "weight": 100,
            "validation_minimum": null,
            "validation_maximum": null,
            "validation_regex": "",
            "choices": [],
            "created": "2023-10-17T12:20:53.892582Z",
            "last_updated": "2023-10-17T12:21:47.628430Z"
        }
    ]
}

Logged in

@pdonias hi there sorry for the late reply.

If I open said link on the browser I get:

@pdonias

Hi there and thank you for your reply.
Well, the error messages aren't exactly equal so to say.

In the image below you can see the result of testing before the XO update was completed (namely the Oct 24 11:11 test was made after update BEFORE reboot/xo restart and 11:16 was after).
So the error message does change slightly.

Oct 24, 11:11

plugin.test
{
  "id": "netbox"
}
{
  "code": 400,
  "url": "https://fw-dea12.domain.tld:8143/api/virtualization/cluster-types/",
  "data": {
    "method": "POST",
    "path": "/virtualization/cluster-types/",
    "body": {
      "name": "[TMP] Xen Orchestra Netbox plugin test - 5qz91pafh",
      "slug": "xo-test-5qz91pafh",
      "description": "This type has been created by Xen Orchestra's Netbox plugin test. If it hasn't been properly deleted, you may delete it manually."
    }
  },
  "message": "Bad Request",
  "name": "Error",
  "stack": "Error: Bad Request
    at onResponse (/opt/xen-orchestra/node_modules/http-request-plus/index.js:255:21)
    at AsyncResource.runInAsyncScope (node:async_hooks:199:9)
    at cb (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:355:42)
    at tryCatcher (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:464:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

And Oct 24, 11:16:

plugin.test
{
  "id": "netbox"
}
{
  "originalUrl": "https://fw-dea12.domain.tld:8143/api/extras/custom-fields/",
  "url": "https://fw-dea12.domain.tld:8143/api/extras/custom-fields/",
  "data": {
    "method": "GET",
    "path": "/extras/custom-fields/"
  },
  "message": "400 Bad Request",
  "name": "Error",
  "stack": "Error: 400 Bad Request
    at Object.assertSuccess (/opt/xen-orchestra/node_modules/http-request-plus/index.js:162:19)
    at httpRequestPlus (/opt/xen-orchestra/node_modules/http-request-plus/index.js:217:22)
    at httpRequest (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:146:26)
    at Netbox.#request (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:183:18)
    at Netbox.#checkCustomFields (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:203:26)
    at Netbox.test (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:106:5)
    at default.testPlugin (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/plugins.mjs:285:5)
    at Xo.test (file:///opt/xen-orchestra/packages/xo-server/src/api/plugin.mjs:109:3)
    at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:417:20)"
}

@pdonias said in Netbox plugin: Error code 400 - Error: Bad Request:

/#/settings/plugins?s=netbox

Netbox 1.3.0

@pdonias thank you for your reply.

I restarted the whole server before actually testing.

the screenshot above was immediately after the build but before the reboot. Was focused on the commit.
Then rebooted, tested, error.

XO up to date now

plugin.test
{
  "id": "netbox"
}
{
  "originalUrl": "https://fw-dea12.domain.tld:8143/api/extras/custom-fields/",
  "url": "https://fw-dea12.domain.tld:8143/api/extras/custom-fields/",
  "data": {
    "method": "GET",
    "path": "/extras/custom-fields/"
  },
  "message": "400 Bad Request",
  "name": "Error",
  "stack": "Error: 400 Bad Request
    at Object.assertSuccess (/opt/xen-orchestra/node_modules/http-request-plus/index.js:162:19)
    at httpRequestPlus (/opt/xen-orchestra/node_modules/http-request-plus/index.js:217:22)
    at httpRequest (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:146:26)
    at Netbox.#request (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:183:18)
    at Netbox.#checkCustomFields (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:203:26)
    at Netbox.test (/opt/xen-orchestra/packages/xo-server-netbox/src/index.js:106:5)
    at default.testPlugin (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/plugins.mjs:285:5)
    at Xo.test (file:///opt/xen-orchestra/packages/xo-server/src/api/plugin.mjs:109:3)
    at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:417:20)"
}

Still giving the same 400 bad request error

@Mark-C

Wouldn't have made it without your help! Super.

So far everything seems to be working normally, except for my original issue on the other topic, posting there now.

If any more issues come up I'll post them here and reference on this topic. Many thanks!!

@Mark-C kudus to you mate. Many thanks for your help, finally got it back.

]# yarn build
yarn run v1.22.19
$ turbo run build --scope xo-server --scope xo-server-'*' --scope xo-web
╭────────────────────────────────────────────────────────────────────────╮
│                                                                        │
│                  Update available v1.10.15 ≫ v1.10.16                  │
│    Changelog: https://github.com/vercel/turbo/releases/tag/v1.10.16    │
│               Run "npx @turbo/codemod update" to update                │
│                                                                        │
│      Follow @turborepo for updates: https://twitter.com/turborepo      │
╰────────────────────────────────────────────────────────────────────────╯
 WARNING  failed to contact turbod. Continuing in standalone mode: connection to turbo daemon process failed.
	To quickly resolve the issue, try running:
	- $ turbo daemon clean

	To debug further - please ensure the following:
	- the process identified by the pid in the file at /tmp/turbod/8288938151d980a6/turbod.pid is not running, and remove /tmp/turbod/8288938151d980a6/turbod.pid
	- check the logs at /root/.local/share/turborepo/logs/8288938151d980a6-xen-orchestra.log
	- the unix domain socket at /tmp/turbod/8288938151d980a6/turbod.sock has been removed

	You can also run without the daemon process by passing --no-daemon
• Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
• Running build in 22 packages
• Remote caching disabled

 Tasks:    26 successful, 26 total
Cached:    0 cached, 26 total
  Time:    2m38.144s 

Done in 159.10s.

Super! Cheers mate!!