I have an Xamp server running on MacOs 10.14.6.
I activated port forwarding on it like that :
localhost:8080 -> 80 (Over SSH)
localhost:8443 -> 443 (Over SSH)
I can navigate to my website on localhost:8443 with no issue.
I have another server running Symfony 5.4 available at localhost:8000. I can navigate to this website with no issue too.
But from the 'Xamp hosted' website, I'm not able to make a request to the 'Symfony hosted' server. I have a "Connection Refused error".
I tried to request both 127.0.0.1:8000 and localhost:8000 : same behavior.
I tried to set the Symfony server to listen to a different port too : same behavior.
It only works when I make a request to the real local ip address (like 192.168.1.34:8000). The problem is that this IP is not stable so I'd like to make the localhost work properly.
What could be the cause of this error ?
What can I do to use localhost hostname for my requests ?
you can disable the task manager section for applications running on the same port which may when you want to request a connection on the server you will use it will get a similar rejection. I think it's more or less like that
Related
I'm new to Web App so I'm sorry if this is a simple question.
I enter: ngrok http 5000
Then when I go to the correct https address I get the message below.
The connection to https://e71eb98330fe.ngrok.io was successfully tunneled to your ngrok client, but the client failed to establish a connection to the local address 127.0.0.1:5000.
Make sure that a web service is running on 127.0.0.1:5000 and that it is a valid address.
The error encountered was: dial tcp 127.0.0.1:5000: connect: connection refused
According to this answer:
I need to set up a web server and point it to local host 5000.
But my error is slightly different and even when I try going to: localhost:5000
It doesn't work.
Is the problem just that I need to point a web server to 5000? How do I do that?
This site can’t provide a secure connection localhost sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
When running a service or site locally you can avoid this problem by doing the following:
In project properties enable SSL:
Make sure to put https link as a start URL or just make direct request to https version:
I have tried setting up SMTP in the dotenv file:
MAILER_URL=smtp://mydomain.nl:25?encryption=tls&username=noreply%mydomain.nl&password=***`
And I've sent an email using php bin/console swiftmailer:email:send. This gave me an error:
[app] Exception occurred while flushing email queue: Connection could not be established with host webmail.mydomain.nl [Connection timed out #110]`
So I assumed this is caused by the firewall. So then I tried to send an email via an online SMTP tester and the email got sent and all worked as expected.
However, this still does not work on my server. Even after turning off the firewall on my (Windows) VPS, the same error persists.
My setup is as follows:
I have a VPS (WINDOWS) with plesk where I host my domain and the mail server.
I also have a home server (CENTOS) where I host my subdomain with plesk.
What am I overlooking? What could be the cause of this issue?
Some host providers block 465 and 25 port. So only 587 is left to use. First, contact your host provider and ask if they are blocking SMTP ports. And if not please come back with more information and server config.
So apparently, please correct me if im wrong. This is what I think I did wrong:
I have a subdomain from my main plesk which I host on my home server. The project i'm working on is running from there.
The main domain with that plesk account is running on a VPS with the mailserver.
As it turns out (I think) my ISP from my home internet has restricted access to port 25. And thats why my home server cant access the mail server.
I tried to disable firewalls everywhere, even routed the ports in my router to my home server, nil fix. (please note that i tried to telnet to several SMTP servers not just my own) with all access rejected.
I tried it with another port (465) from my home server and it works now.
At the end using another port did the trick. I am however not sure that this is the issue. But this is just my guess.
Note - I am fully aware that there are lot of similar issues posted before, but I tried NSG settings, psping but nothing seem to work
All, I brought up a RHEL7.3 server on Azure and installed JDK1.8 and Tomcat8. After starting Tomcat, I tried an http request from my browser:
http://XX.yy.zz.abc:8080/ but I was unable to get the index page
I also created an inbound security rule to allow HTTP and also allow IP range from our company.
Even worse is, when I tried pinging to this IP from my desktop computer, I am unable to ping the same - it is timing out.
Please note that in the past, I've been able to bring up servers and be able to connect from desktops without any issues - in a similar azure-companynetwork setup.
Am I missing anything here?
Ok, so pings do not work, you shouldn't even try that. What you should check is the firewall on you RHEL VM and check you've allowed port 8080 on you NSG, also your VM should have a PublicIP attached
According to your description, you had better check as the following ways:
1.Please ensure you could access your web by using 127.0.0.1:8080 on your VM.
2.Check your service listening.
netstat -ant|grep 8080
Please ensure 8080 is listening on tcp not tcp6.
3.Open firewall port on RHEL.
sudo firewall-cmd --zone=public --add-port=8080/tcp --permanent
More information about RHEL firewall please refer to this link.
4.Open port on Azure NSG.
NSG could be associated with NIC and subnet, you should check all of them.
All,
It looks like there is an input firewall inside of RHEL7.3 that is preventing connections. I just stopped it using
service firewalld stop
I am able to get the home page.
I am trying to get GitLab setup with my current installation of Nginx but I keep getting an Error 502. I have included my configuration files, and not sure what I am doing wrong. But I followed the "Using a non-bundled web-server" steps on https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/nginx.md
/etc/nginx/conf.d/gitlab-omnibus-nginx.conf
http://pastebin.com/bQ8eCiNh
/etc/gitlab/gitlab.rb
http://pastebin.com/Lw5tjwXy
HTTP 502 means "The server was acting as a gateway or proxy and received an invalid response from the upstream server." So there are two possibilities here.
Your Gitlab server is not actually working or is returning an invalid response. After starting the Gitlab server, use sudo netstat -plnt and make sure it is running on a port and note the port. Then connect directly to this port in your browser (or from the CLI on the server if necessary) and confirm that Gitlab is working fine without a proxy in front of it. If Gitlab is running on a socket and not a port, there are also tools to test HTTP servers through socket connections that you can use.
Nginx is not configured correctly to connect to Gitlab. In this case, check your Nginx error log to see if there is any more detail besides the "502" error.