Custom Field API Patch - 504 gateway timeout #13879

jnc27 · 2023-09-25T07:48:16Z

jnc27
Sep 25, 2023

Hi,
when trying to update a custom field via a netbox script, I get a 504 gateway timeout. I'm triggering the update with API requests.patch on the same device, but I get a 504 gateway timeout.

PATCH /api/dcim/devices/11023/ HTTP/1.1
Host: 10.x.x.x
User-Agent: python-requests/2.31.0
Accept-Encoding: gzip, deflate
Accept: */*
Connection: keep-alive
Content-Type: application/json
Authorization: Token xxxxxxxxx
Content-Length: 67

{"custom_fields": {"TEST": "TEST"}}HTTP/1.1 504 Gateway Time-out
Server: nginx/1.20.1
Date: Mon, 25 Sep 2023 06:51:44 GMT
Content-Type: text/html
Content-Length: 167
Connection: keep-alive

<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.20.1</center>
</body>
</html>

When trying to do the same with curl on the same machine - it works.

Is there a setting somewhere which does not allow me to update values when using netbox Script on the same machine?
Thanks!

Netbox Version: 3.6.2

jnc27 · 2023-09-26T05:56:18Z

jnc27
Sep 26, 2023
Author

The nginx error log says the following:
2023/09/25 13:43:11 [error] 1226#1226: *98 upstream timed out (110: Connection timed out) while reading response header from upstream, client: x.x.x.x server: netbox02.local request: "PATCH /api/dcim/devices/11023/ HTTP/1.1", upstream: "http://127.0.0.1:8001/api/dcim/devices/11023/", host: "x.x.x.x"

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Custom Field API Patch - 504 gateway timeout #13879

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Custom Field API Patch - 504 gateway timeout #13879

Uh oh!

Uh oh!

jnc27 Sep 25, 2023

Replies: 1 comment

Uh oh!

jnc27 Sep 26, 2023 Author

jnc27
Sep 25, 2023

jnc27
Sep 26, 2023
Author