Trying to switch pages in rack elevations throws error: htmx:targetError #11275

Closed
opened 2025-12-29 21:42:46 +01:00 by adam · 4 comments
Owner

Originally created by @SoLoR1 on GitHub (Jun 9, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.2

Python Version

3.12

Steps to Reproduce

  1. Have a location with more then 25 racks
  2. Go to rack elevations
  3. Try to switch to page2 to see racks after 25

Expected Behavior

Being able to switch to page2 (or more), without workaround (you can copy link and go to that link)

Observed Behavior

Error in console:

Image

htmx.esm.js:3013 htmx:targetError
logError @ htmx.esm.js:3013
triggerEvent @ htmx.esm.js:3040
triggerErrorEvent @ htmx.esm.js:2981
issueAjaxRequest @ htmx.esm.js:4188
(anonymous) @ htmx.esm.js:2383
l @ htmx.esm.js:2545

Originally created by @SoLoR1 on GitHub (Jun 9, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.2 ### Python Version 3.12 ### Steps to Reproduce 1. Have a location with more then 25 racks 2. Go to rack elevations 3. Try to switch to page2 to see racks after 25 ### Expected Behavior Being able to switch to page2 (or more), without workaround (you can copy link and go to that link) ### Observed Behavior Error in console: ![Image](https://github.com/user-attachments/assets/e8133adf-83a1-4196-afbb-dd0276e4116d) htmx.esm.js:3013 htmx:targetError logError @ htmx.esm.js:3013 triggerEvent @ htmx.esm.js:3040 triggerErrorEvent @ htmx.esm.js:2981 issueAjaxRequest @ htmx.esm.js:4188 (anonymous) @ htmx.esm.js:2383 l @ htmx.esm.js:2545
adam added the type: bugpending closurestatus: revisions needed labels 2025-12-29 21:42:46 +01:00
adam closed this issue 2025-12-29 21:42:47 +01:00
Author
Owner

@jnovinger commented on GitHub (Jun 9, 2025):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v4.3.2 (main branch checkout). Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

@jnovinger commented on GitHub (Jun 9, 2025): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v4.3.2 (`main` branch checkout). Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.
Author
Owner

@SoLoR1 commented on GitHub (Jun 9, 2025):

I forgot to add im using docker and nginx as a proxy to it (proxy is not at fault, since i tried direct connection and it is the same).

Image

Also this is netboxcommunity/netbox:latest-plugins (since i also use few plugins), however i turned off all plugins and also switched to netboxcommunity/netbox:latest and it is the same.

I did also try demo version that you have and all is working as it should there.

How inital objects and other data was created, i have no idea it was a year ago.

I will try some things....

@SoLoR1 commented on GitHub (Jun 9, 2025): I forgot to add im using docker and nginx as a proxy to it (proxy is not at fault, since i tried direct connection and it is the same). ![Image](https://github.com/user-attachments/assets/1ad4ed2c-e814-4fa4-b63b-c2ad306022c0) Also this is netboxcommunity/netbox:latest-plugins (since i also use few plugins), however i turned off all plugins and also switched to netboxcommunity/netbox:latest and it is the same. I did also try demo version that you have and all is working as it should there. How inital objects and other data was created, i have no idea it was a year ago. I will try some things....
Author
Owner

@github-actions[bot] commented on GitHub (Jun 17, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Jun 17, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
Author
Owner

@github-actions[bot] commented on GitHub (Jun 24, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Jun 24, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11275