starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Dashboard: 504 Gateway Time-out #11915

New Issue
Closed
opened 2025-12-29 21:51:28 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:51:28 +01:00
Owner
Copy Link

Originally created by @ecoutinho on GitHub (Dec 10, 2025).

NetBox Edition

NetBox Community

NetBox Version

v4.4.8

Python Version

3.12

Steps to Reproduce

Login to Netbox

Expected Behavior

It should show the initial dashboard.

Observed Behavior

It returns a nginx timeout error.

It turns out that I have a RSS feed widget on my initial dashboard, but currently there's an issue on https://netbox.dev/rss/ certificate, which prevents the page from loading. In turn, this prevents Netbox from loading the dashboard. The RSS widget should not prevent the dashboard from loading.

If I access an inner page, such as /dcim/sites, everything works fine.

PS: The certificate on netbox.dev was issued to "tom-01.netbox.dev" and it doesn't have "netbox.dev" as one of its DNS names.

Originally created by @ecoutinho on GitHub (Dec 10, 2025). ### NetBox Edition NetBox Community ### NetBox Version v4.4.8 ### Python Version 3.12 ### Steps to Reproduce Login to Netbox ### Expected Behavior It should show the initial dashboard. ### Observed Behavior It returns a nginx timeout error. It turns out that I have a RSS feed widget on my initial dashboard, but currently there's an issue on https://netbox.dev/rss/ certificate, which prevents the page from loading. In turn, this prevents Netbox from loading the dashboard. The RSS widget should not prevent the dashboard from loading. If I access an inner page, such as /dcim/sites, everything works fine. PS: The certificate on netbox.dev was issued to "tom-01.netbox.dev" and it doesn't have "netbox.dev" as one of its DNS names.
adam added the netbox label 2025-12-29 21:51:28 +01:00
adam closed this issue 2025-12-29 21:51:28 +01:00
adam commented 2025-12-29 21:51:29 +01:00
Author
Owner
Copy Link

@ecoutinho commented on GitHub (Dec 10, 2025):

I've disabled HTTP_PROXIES and set ISOLATED_DEPLOYMENT = True in configuration, but the widget still tries to load the RSS feed. tcpdump shows it's not using the proxy, but trying to connect directly to netbox.dev, ignoring the ISOLATED_DEPLOYMENT setup.

As I can't load the dashboard page, is there any way to disable the widget?

@ecoutinho commented on GitHub (Dec 10, 2025): I've disabled HTTP_PROXIES and set `ISOLATED_DEPLOYMENT = True` in configuration, but the widget still tries to load the RSS feed. tcpdump shows it's not using the proxy, but trying to connect directly to netbox.dev, ignoring the ISOLATED_DEPLOYMENT setup. As I can't load the dashboard page, is there any way to disable the widget?
adam commented 2025-12-29 21:51:29 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Dec 12, 2025):

@ecoutinho, as a very temporary workaround, you have a few options to remove the widget from your user's layout:

  1. Via the REST API at /api/extras/dashboard. GET to inspect what's there, PATCH to modify.
  2. Update the definition of DEFAULT_DASHBOARD in your configuration.py module and remove the RSS widget, then navigate to https://<netbox>/extras/dashboard/reset/ to re-populate it.
  3. Via direct manipulation of NetBox's models in manage.py shell. This has next to no guardrails, so it only makes sense if your comfortable working with Django models in the REPL.
  4. Via direct SQL, you can modify the Dashboard.layout and Dashboard.config associated with your user. Same caveat here, this has the fewest guardrails and should be the last resort.

The REST API option is probably the safest option, providing validation of updated values. The DEFAULT_DASHBOARD route has the drawback of potentially affecting all users, which may or may not be intended. The direct model manipulation and SQL options are the least safe and should be, I think, you're last option.

@jnovinger commented on GitHub (Dec 12, 2025): @ecoutinho, as a very temporary workaround, you have a few options to remove the widget from your user's layout: 1. Via the REST API at `/api/extras/dashboard`. GET to inspect what's there, PATCH to modify. 2. Update the definition of `DEFAULT_DASHBOARD` in your `configuration.py` module and remove the RSS widget, then navigate to `https://<netbox>/extras/dashboard/reset/` to re-populate it. 3. Via direct manipulation of NetBox's models in `manage.py shell`. This has next to no guardrails, so it only makes sense if your comfortable working with Django models in the REPL. 4. Via direct SQL, you can modify the `Dashboard.layout` and `Dashboard.config` associated with your user. Same caveat here, this has the fewest guardrails and should be the last resort. The REST API option is probably the safest option, providing validation of updated values. The `DEFAULT_DASHBOARD` route has the drawback of potentially affecting all users, which may or may not be intended. The direct model manipulation and SQL options are the least safe and should be, I think, you're last option.
adam commented 2025-12-29 21:51:29 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Dec 12, 2025):

Please re-check the cert issue. I am not able to reproduce.

Also, it looks like the widget URL was updated to https://api.netbox.oss.netboxlabs.com/v1/newsfeed/ in v4.2.3.

@jnovinger commented on GitHub (Dec 12, 2025): Please re-check the cert issue. I am not able to reproduce. Also, it looks like the widget URL was updated to https://api.netbox.oss.netboxlabs.com/v1/newsfeed/ in [v4.2.3](https://github.com/netbox-community/netbox/pull/18506).
adam commented 2025-12-29 21:51:29 +01:00
Author
Owner
Copy Link

@ecoutinho commented on GitHub (Dec 12, 2025):

Thanks for the detailed reply! I ended up taking the DEFAULT_DASHBOARD option and reset the dashboard.

On the cert issue, I can't reproduce it either. Today the reply I'm getting has a valid certificate issued in October, while two days ago the certificate I got had been issued a couple of days ago. The only issue I see today, is one of the three IPs (134.199.240.230) in roundrobin not responding:

$ wget https://netbox.dev/rss/
--2025-12-12 17:11:19--  https://netbox.dev/rss/
Resolving netbox.dev (netbox.dev)... 13.248.160.137, 76.223.34.124, 134.199.240.230
Connecting to netbox.dev (netbox.dev)|13.248.160.137|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://netboxlabs.com/feed [following]

$ wget https://netbox.dev/rss/
--2025-12-12 17:11:21--  https://netbox.dev/rss/
Resolving netbox.dev (netbox.dev)... 134.199.240.230, 13.248.160.137, 76.223.34.124
Connecting to netbox.dev (netbox.dev)|134.199.240.230|:443... failed: Connection timed out.

Anyway, this was not the main issue, which is now solved, so I'm closing the request. Thanks for your support.

@ecoutinho commented on GitHub (Dec 12, 2025): Thanks for the detailed reply! I ended up taking the `DEFAULT_DASHBOARD` option and reset the dashboard. On the cert issue, I can't reproduce it either. Today the reply I'm getting has a valid certificate issued in October, while two days ago the certificate I got had been issued a couple of days ago. The only issue I see today, is one of the three IPs (134.199.240.230) in roundrobin not responding: ``` $ wget https://netbox.dev/rss/ --2025-12-12 17:11:19-- https://netbox.dev/rss/ Resolving netbox.dev (netbox.dev)... 13.248.160.137, 76.223.34.124, 134.199.240.230 Connecting to netbox.dev (netbox.dev)|13.248.160.137|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://netboxlabs.com/feed [following] ``` ``` $ wget https://netbox.dev/rss/ --2025-12-12 17:11:21-- https://netbox.dev/rss/ Resolving netbox.dev (netbox.dev)... 134.199.240.230, 13.248.160.137, 76.223.34.124 Connecting to netbox.dev (netbox.dev)|134.199.240.230|:443... failed: Connection timed out. ``` Anyway, this was not the main issue, which is now solved, so I'm closing the request. Thanks for your support.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label netbox
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11915
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?