Wrong FQDN on racks devices after upgrade #3578

Closed
opened 2025-12-29 18:29:59 +01:00 by adam · 1 comment
Owner

Originally created by @ilyamoshkin on GitHub (Apr 16, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.8.0

Steps to Reproduce

  1. Upgrade 2.5.13 up to 2.8.0.
  2. Take errors with "extras_tag.comments does not exist" and like "unsupported PGSQL version".
  3. Downgrade to 2.6.0 and then again upgrade to 2.8.0.

Expected Behavior

Normal FQDN in focus on racked devices.

Observed Behavior

https://netbox.backend/ in FQDN part of URL where netbox is the 3rd lvl name.
Please help how to fix that.

Originally created by @ilyamoshkin on GitHub (Apr 16, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report, and that any plugins have been disabled. --> ### Environment * Python version: 3.6.8 * NetBox version: 2.8.0 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. Upgrade 2.5.13 up to 2.8.0. 2. Take errors with "extras_tag.comments does not exist" and like "unsupported PGSQL version". 3. Downgrade to 2.6.0 and then again upgrade to 2.8.0. <!-- What did you expect to happen? --> ### Expected Behavior Normal FQDN in focus on racked devices. <!-- What happened instead? --> ### Observed Behavior https://**netbox.backend**/ in FQDN part of URL where netbox is the 3rd lvl name. Please help how to fix that.
adam closed this issue 2025-12-29 18:29:59 +01:00
Author
Owner

@kobayashi commented on GitHub (Apr 17, 2020):

Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using one of the templates provided here. For general discussion, questions, or assistance with installation issues, please post to our mailing list instead.

@kobayashi commented on GitHub (Apr 17, 2020): Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using one of the templates provided [here](https://github.com/digitalocean/netbox/issues/new/choose). For general discussion, questions, or assistance with installation issues, please post to our [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss) instead.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3578