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

EDT timezone causes 502 Bad Gateway error #8183

New Issue
Closed
opened 2025-12-29 20:33:33 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:33:33 +01:00
Owner
Copy Link

Originally created by @BH-NetAdmin on GitHub (Jun 9, 2023).

NetBox version

v3.5.3

Python version

3.10

Steps to Reproduce

set time zone to EDT in configuration.py and restart netbox service

Expected Behavior

for netbox to accept EDT timezone and not error out

Observed Behavior

502 Bad Gateway when trying to access netbox

Originally created by @BH-NetAdmin on GitHub (Jun 9, 2023). ### NetBox version v3.5.3 ### Python version 3.10 ### Steps to Reproduce set time zone to EDT in configuration.py and restart netbox service ### Expected Behavior for netbox to accept EDT timezone and not error out ### Observed Behavior 502 Bad Gateway when trying to access netbox
adam added the type: bug label 2025-12-29 20:33:33 +01:00
adam closed this issue 2025-12-29 20:33:33 +01:00
adam commented 2025-12-29 20:33:34 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jun 11, 2023):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@abhi1693 commented on GitHub (Jun 11, 2023): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 20:33:34 +01:00
Author
Owner
Copy Link

@stuntguy3000 commented on GitHub (Jun 11, 2023):

Adding to this, @BH-NetAdmin please try to use a timezone from https://en.wikipedia.org/wiki/List_of_tz_database_time_zones.

It sounds like you've entered "EDT", which would be invalid. NetBox will not boot, and then the 502 will be returned from the reverse proxy because NetBox isn't running.

@stuntguy3000 commented on GitHub (Jun 11, 2023): Adding to this, @BH-NetAdmin please try to use a timezone from https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. It sounds like you've entered "EDT", which would be invalid. NetBox will not boot, and then the 502 will be returned from the reverse proxy because NetBox isn't running.
adam commented 2025-12-29 20:33:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 12, 2023):

As @stuntguy3000 points out, the list of valid timezones is referenced in the documentation for the config parameter. "EDT" is not a valid timezone.

@jeremystretch commented on GitHub (Jun 12, 2023): As @stuntguy3000 points out, the list of valid timezones is referenced in [the documentation for the config parameter](https://docs.netbox.dev/en/stable/configuration/date-time/#time_zone). "EDT" is not a valid timezone.
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 type: bug
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#8183
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?