How to fix the localhost:8080 (502 Bad Gateway) problem - tomcat8

I downloaded Tomcat 8 on my Mac and I started it up but when I go to the browser and enter localhost:8080 it gives me a 502 Bad gateway error that says:
Socks5ProtocolException("SOCKS5 mode failure: SocksError('Invalid SOCKS version. Expected 0x05, got 0x47',)",)
how can I fix this problem?
It was working fine but after a few days, it started to give me this error. is it okay to just change the default port o for example 8081? or I will need that 8080 port at some point?
thanks in advance.

Related

HAproxy fails to start after changing ssl certificates

I've been struggling with this issue for 2 days now and it's starting to be a big problem.
we have 2 LB on which HAproxy is installed,
I've tried to change the certificats on the first one and it fell down and couldn't restart it even when getting back the old haproxy.cfg file.
after a while I tried to restart the server and it did the job. I had my Haproxy running on the failed node. and I successfully changed the ssl certificats on that one.
Then, I tried to do the same on the second, and then it went down and nothing seem to be correcting the problem; not restarting haproxy on the old haproxy.cfg file nor restarting the whole server.
the error I get is like this :
Starting frontend PAGEMAINTENANC_GUN: cannot bind socket [10.168.10.16:80]
Can you please give me some little help?
thank you all in advance.
It seems that I've been trying to bind to an IP address that is not local. That's why the HAproxy fails to start. The solution was to set ip_nonlocal_bind to 1.
To get info:
sysctl net.ipv4.ip_nonlocal_bind
Set net.ipv4.ip_nonlocal_bind to 1
sysctl -w net.ipv4.ip_nonlocal_bind=1
Restart HAproxy works

111: Connection refused while connecting to upstream

I tried to duplicate my .NET Core Linux environment from this question to have 2 environments, and the logs say
Now listening on: http://[::]:5000
which makes me think it is working, but the requests get this error:
(111: Connection refused) while connecting to upstream, client:
172.31.44.219, server: , request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:5000/", host: "172.31.47.124"
And it times out. I believe everything is the same, while the initial environment is working perfectly fine. I created this one without "configuring more options" so it is not part of a VPC etc but neither is my initial environment. What should I be checking? I have viewed some answers on here for this issue but no fixes worked. For example, I commented out app.UseHttpsRedirection(); but still have the issue.
Okay, so I have noticed that EB creates and attaches a security group, and it listens on port 80, not 5000. I am leaving this here as it might be helpful for someone else (aka my future self).

How can I troubleshoot Docker pull failing with HTTP 503 error?

I’ve used docker some in the past , I’m trying to introduce it at a new environment, but cannot get docker pull working. Keeps failing with 503 response.
What I could use help with is finding the underlying cause of this issue, so I can have the net/it admins fix whatever it is, be it firewall, ssl, proxy authentication, (all the usual suspects running docker/windows in a corporate network, ya know.)
Where can I look to see the root cause of pull failures to help them out? Also any specific diagnostic tests I could run to help figure this out would help.
I am able to hit registry-1.docker.io in general:
e.g.
curl https://registry-1.docker.io/v2/
{“errors”:[{“code”:“UNAUTHORIZED”,“message”:“authentication required”,“detail”:null}]}
I’ve poked through the logs in %localappdata%/docker, but have not been able to find anything.
the only thing I found at all was in dockerd.log:
2021-08-19T13:59:06Z dockerd time=“2021-08-19T13:59:06.656666400Z” level=debug msg="pulling blob “sha256:9da81141e74e38839836e81c2691d3c7ac54bf34272e5d4a636fc032150506a4"”
2021-08-19T13:59:06Z dockerd time=“2021-08-19T13:59:06.994330700Z” level=info msg=“Download failed, retrying (1/5): received unexpected HTTP status: 503 Service Unavailable”
Which does not really help. I know docker registry is not down, so this is not really a 503 from docker.
System info
OS: Windows 10 19043, WSL2 enabled (VM with virtualization enabled, if that matters)
Docker version 20.10.7, build f0df350
repro steps:
docker run -d -p 80:80 docker/getting-started
Unable to find image ‘docker/getting-started:latest’ locally
latest: Pulling from docker/getting-started
540db60ca938: Retrying in X seconds (repeats countdown a few times with increasing wait times )
0ae30075c5da: Retrying in X seconds
9da81141e74e: Retrying in X seconds
b2e41dd2ded0: Waiting
7f40e809fb2d: Waiting
758848c48411: Waiting
23ded5c3e3fe: Waiting
38a847d4d941: Waiting
docker: received unexpected HTTP status: 503 Service Unavailable. (finally)
See ‘docker run --help’.
Thanks.
JS
Answering my own question: I ran docker through fiddler, by setting the docker proxy to localhost:8888. Inspecting the body of the 503 response in fiddler, I was able to see the cause: The corporate firewall rules were blocking executable file transfers.

Tomcat 8.5 fails connection to localhost/8080

I am running Apache Tomcat 8.5. After I start tomcat, I enter the address http://localhost/8080/ in the browser address bar but it gives me the following error :
How do I solve this error and get tomcat running normally ?
The link(url) http://localhost/8080/ you are using to access the tomcat page is wrong.
It should be http://localhost:8080. Please try.

XAMPP,Apache - Error: Apache shutdown unexpectedly

I got the same error of shutdown unexpectedly. I tried everything.
I uninstalled skype.
I tried changing the ports to 81,444 / 81,443 / 88/443 / 80,443(default).
I went to services and tried killing required one.
I went to windows firewall and created the new inbound rule too.
I uninstalled old apache and installed new one too. This worked for 1 day.
I checked whether the port 80 is busy or not but none of the services is using port
80,443. I used netstat -a command to check all the list of port for Win-8.
I tried stopping windows http services by "NET STOP HTTP".
I unchecked "Internet Information Services" from program and features.
I checked "Resource Monitor" for port usage. Port 80 is being used by HTTP server only
but not responding to xampp control panel.
In all of the above cases, I made the changes and restarted the laptop every time to take the effect. But nothing has worked. Each time i got the same error i.e "XAMPP, Apache - Error: Apache shutdown unexpectedly".
Please give me the solution for this error. I am very much frustrated now. Please help me. Any help would be appreciable. Thank you in advance.
It would be good if you enable Apache Logs in debug mode.
LogLevel debug
Also you can get easily notified for syntax issues with help of below command.
httpd -t
For your skype, go to Tools -> Options -> Advanced -> connection. Disable the "Use port 80 and 443 for alternatives for incoming connections"
Sign Out and Close all Skype windows. Try restart your Apache again.