Bad Request. INTERNAL SERVICE ERROR on pgadmin4 on docker - postgresql

I installed pgadmin4 and postgres on my VPS successfully, but I got this error. I could not found the solution on internet either. What is the cause of the error, and how can the problem be fixed?
Installing instruction: https://github.com/khezen/compose-postgres/blob/master/docker-compose.yml
The error dialog just says "Bad Request", and I get a notification at the bottom right in red that there was an "INTERNAL SERVICE ERROR".
Here's a screenshot so you can see what I see.

Related

Supervisor "spawn error" : I'm stuck... how can I know the reason for the error?

I have a Django REST API running on an UBUNTU 20.04 server, with a sqlite database.
Everything has been working for weeks with no issue.
Today, after pulling small changes to my code (changes in my settings.py file), I've tried to restart the GUNICORN server with SUPERVISOR as usual with:
sudo supervisorctl restart <MyAppName>
but I get an error message :
<MyAppName>-gunicorn: ERROR (spawn error)
In /var/log/supervisor.supervisor.log, I can only see that error message :
exited: <MyApp>-gunicorn (exit status 3; not expected)
I can find no way to have it working again (I've even tried to restart the server).
The strange thing is that when I manually launch gunicorn with :
/home/<myname>/env/bin/gunicorn <MyApp>.wsgi
I have no error message and my server works perfectly(requests are served to my app).
How can I know the reason for the supervisor spawn error ?

runtime error due to sock_open failure TPM-Emulator

I've recently setup and installed (after much finicking around to get around the seemingly common SSL error) the Mario Strasser TPM emulator.
Setting it up to run with modprobe tpmd_dev and then tpmd worked fine, however, once it was running I wanted to begin working on some code to interact with it and ran the test_tddl file, only to find that it fails to open the /dev/tpm file. after a little digging around I've found that it's a failure due to a sock_connect() call fails. Have I gone wrong with setting up the emulator somewhere? I'm running on ubuntu 16.04 on a virtual box VM
The error given upon running test_tddl is Error: Tddli_Open() failed: operation failed (0002)
and the error given in dmesg isError: sock_connect() failed: -2
Im an idiot, if anyone else runs into this problem, ensure that your running both tpmd and test_tddl as root, or else the programs will be unable to open the socket required.

Error 422 after installing gitlab on centos 7

I got into trouble after installing Gitlab on CentOs7. For the first time I was redirected to the admin password creation page and after the password for the admin user, the server sent error.
422
The change you requested was rejected.
I had set the url value based on the site guide.
Set the external_url in /etc/gitlab/gitlab.rb:
external_url "https://example.com/gitlab"
I checked the links below for similar situations. I didn't find the right answer. My server was in the local area and had no internet access.
Error 422 after installing gitlab on Ubuntu 18.04
After Update Error: "422 The change you requested was rejected."
Error 422 after installing Gitlab on Ubuntu 16.04
I made a mistake when installing Gitlab. In the /etc/gitlab/gitlab.rb file I put the local gitlab address with https but due to the local server setup there was no "let's encrypt" service and I did not intend to access the site via ssl. I modified the address in the file and turne "https" to "http". After modifying the following commands, the problem was fixed.
sudo gitlab-ctl reconfigure
sudo gitlab-ctl restart

Eclipse Che Websocket Unable to Establish Connection

I'm running Che on WS2019 under Docker for Windows. When starting Che using the call from the guide (see copy below, custom port added) it pulls the container and sets it up all ok.
docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /chedata:/data -e CHE_PORT=8090 eclipse/che start
When I open Che and go to the workspace (localhost:8090) to create a project, the create button is greyed out, and the browser console has the below errors.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://wsagent-http-dev-machine-workspacel90axz6gl3kl3mzl.192.168.1.100.nip.io:8090/api/project-type. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Firefox can’t establish a connection to the server at ws://localhost:32845/wsagent?token=. playground:18015:24
ERROR (org.eclipse.che.ide.projecttype.ProjectTypeRegistryImpl): Can't load project types: org.eclipse.che.ide.commons.exception.ServerDisconnectedException _app-0.js:17942:126
WARNING (org.eclipse.che.ide.websocket.impl.BasicWebSocketEndpoint): Error occurred for endpoint ws://localhost:32845/wsagent?token= _app-0.js:17942:126
Firefox can’t establish a connection to the server at ws://localhost:32845/wsagent?token=. playground:18015:24
WARNING (org.eclipse.che.ide.websocket.impl.BasicWebSocketEndpoint): Error occurred for endpoint ws://localhost:32845/wsagent?token=
To keep firewalls out of the issue, I've disabled windows firewall. Initially I have tried to fix the CORS issue by using CHE_CORS_ENABLED with no such luck.
I've tried specifying CHE_HOST and CHE_DOCKER_IP_EXTERNAL flags with effectively the same result. I have also tried using CHE_SINGLE_PORT=true, with again a similar issue.
I've looked at a lot of the other GitHub issues reported on Che (e.g. https://github.com/eclipse/che-dockerfiles/pull/11) and have been going at this for a good few days to no avail.
Any suggestions would be helpful,
Inci

Problem creating REST API With JSON Server

I am going through the tutorial: https://www.youtube.com/watch?v=x3NAo8zqdmo
to set up json server. I am able to install it, however when I run the command json-server --watch db.json, I keep getting error
events.js:183
throw er: //unhandled 'error' event
I googled the error, there is nothing running on port 3000 . I even rebooted my machine but error did not go away.
I reinstalled json-server using my company's proxy settings to go behind proxy settings since I had to do that for angular cli installation, but still error is not going away. Any tips?
I was able to resolve the issue by changing the port with command
json-server -p 4000 db.json