Bad Request Error when Adding new users and devices

[SnowTail101]

Hi

I recently installed Netbox on a local server and am trying to get started with adding items. I noticed that I get a Bad Request Error when adding new devices or users etc in Netbox online interface. I am signed in with the superuser account. My colleague who also logs in with the same superuser account on his machine doesn't have this issue. Are there any restrictions on the superuser account login? Does one machine take priority over another for instance? Any advice to get around this issue will me much appreciated.

Netbox Version is v3.6.2
I am using both IE and Chrome browsers. same issue when using a private window and after clearing cookies and cache from the browsers.

[candlerb]

There are no restrictions on superuser.

You have a problem, but you've haven't shown any details of the problem (e.g. what error you see). Nor have you said what version of Netbox you're using.

Without that information, it's impossible to guess what's wrong with your system.

[SnowTail101]

I have now updated the question. Thanks for pointing out the missing info. First post asking for help

[candlerb]

Do you have any logs from Netbox or from Nginx? 400 is just a generic "the client sent an invalid request" error.

A 400 error can commonly be returned if:

1. You haven't set ALLOWED_HOSTS in configuration.py to match the hostname you're connecting to (compare this setting with what's in your browser's URL bar)
2. You haven't configured Nginx properly to set the X-Forwarded-Host: header. You can find a valid sample nginx.conf here.

However, since the 400 error page appears to be generated by Nginx itself, it might be something else.

[SnowTail101]

thank you for your response, very good suggestions;

1. ALLOWED_HOSTS setting didn't seem to make a difference, I tried both asterisk '*' and matching the url
2. nginx.conf settings all look good

The fact that another colleague can login with the superuser account and doesn't see this problem, feels like the setup is all working ok in general and this is a local machine issue. To check, I tried to login with at different user credentials, the issue pursues. I am the main administrator and need to start creating tokens etc. at the moment it is not possible. The only other thing I can try is testing it on other machines in the office..

[mtinberg]

I know this sounds basic, but have you tried resetting your browser cache, or using an incognito window to test. I've had some very​ strange behavior from webapps on occasion due to incorrectly cached assets or cookies. — Mark Tinberg ***@***.***> Division of Information Technology-Network Services University of Wisconsin-Madison

…

________________________________ From: SnowTail101 ***@***.***> Sent: Friday, November 3, 2023 8:08 AM To: netbox-community/netbox ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [netbox-community/netbox] Bad Request Error when Adding new users and devices (Discussion #14177) thank you for your response, very good suggestions; 1. ALLOWED_HOSTS setting didn't seem to make a difference, I tried both asterisk '*' and matching the url 2. nginx.conf settings all look good The fact that another colleague can login with the superuser account and doesn't see this problem, feels like the setup is all working ok in general and this is a local machine issue. To check, I tried to login with at different user credentials, the issue pursues. I am the main administrator and need to start creating tokens etc. at the moment it is not possible. The only other thing I can try is testing it on other machines in the office.. — Reply to this email directly, view it on GitHub<#14177 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAS7UM4IU47YP3JMRHHWO4LYCTUDNAVCNFSM6AAAAAA63NZJGWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINRWHE4DC>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[SnowTail101]

Hi Mark. Yes, I know what you mean with cache and cookies. Unfortunately, I have tried those already and didn't fix the problem. I was convinced that would have been the issue but no luck.

[SnowTail101]

I have resolved the issue; it was due to the web browsers. Both Edge and Chrome is still giving the error despite clearing cache and cookies multiple times. I have installed a third browser and it is running fine on Firefox browser. Thank you everyone for your suggestions, I will close this now.