Bad Request in Webbrowser (400) after moving OpenRem Docker VM into another Network

22 views
Skip to first unread message

Antonio Flores

unread,
Feb 26, 2025, 6:30:56 AMFeb 26
to OpenREM
Dear community,

I am running OpenREM Docker in the newest available version in a Debian VM in ProxMox. 
I had to move the VM into another Network. There all docker containers are running normal, but browser requests get an error 400 (Bad Request).  
Recreating all docker containers did not help.
Curl -v of the webpage and the nginx docker log show the same error without more details.

Has anybody an idea where else to look?
Help appreciated
Anton

Antonio Flores

unread,
Feb 26, 2025, 6:34:35 AMFeb 26
to OpenREM
To rule out network issues I installed docker portainer in this VM. The web interface shows up normal.

Ed McDonagh

unread,
Feb 26, 2025, 7:06:19 AMFeb 26
to OpenREM
Hi Antonio

Do you know that your requests are arriving at the nginx container - do the docker nginx logs show the activity? What do they say?

Kind regards

Ed

--
You received this message because you are subscribed to the Google Groups "OpenREM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrem+u...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/openrem/67999b2e-f993-4327-876e-6fb713d36321n%40googlegroups.com.

Antonio Flores

unread,
Feb 26, 2025, 7:18:40 AMFeb 26
to OpenREM
Hi Ed,
yes. "docker logs openrem-nginx" shows also the error: "GET / HTTP/1.1" 400 154 "

Ed McDonagh

unread,
Feb 26, 2025, 7:47:37 AMFeb 26
to OpenREM
Is your https://bitbucket.org/openrem/docker/src/develop/nginx-conf/conf.d/openrem.conf file still in the folder and is it still being mapped by your docker-compose.yml file?

Ed McDonagh

unread,
Feb 26, 2025, 8:04:27 AMFeb 26
to OpenREM
Can you please review your .env.prod file for me please?

  1. There is an option to set the DEBUG mode on - set to 1 instead of 0. This should enable a response with details of the error hopefully.
  2. I think the issue will be that the IP address you are now using is not listed in DJANGO_ALLOWED_HOSTS
You will need to restart the containers after you have made any changes.

Antonio Flores

unread,
Feb 26, 2025, 2:02:48 PMFeb 26
to OpenREM
Thank you Ed! You are my hero :-)

DJANGO_ALLOWED_HOSTS hat to be adjusted to the new host.

Reply all
Reply to author
Forward
0 new messages