Results 1 to 5 of 5

Thread: ERR_CONNECTION_REFUSED on intranet

  1. #1

    Default ERR_CONNECTION_REFUSED on intranet

    Hi,

    I have upgraded my OS to version 13.2, and I have a web-development server in VirtualBox installed with Vagrant. Since the upgrade, if I try to open my works in a browser, I get this error: ERR_CONNECTION_REFUSED.

    I have tried the followings:
    • Checked the /etc/hosts file if it has got overwritten during the upgrade. No, it still contains my "192.168.56.101 www.awesome.dev" entry.
    • Tried to shut down the firewall. The problem still exists.
    • Tried to disable AppArmor, it did not work either.
    • Tried to disable both AppArmor and firewall at the same time, still no success.
    • Pinged www.awesome.dev: successfully connected, so my server, no doubt, really exists.
    • SSHed with "vagrant ssh", it also worked.
    • Tried to destroy the server and "vagrant up" again, but still no success.
    • Tried to make a clean install of openSUSE 13.2 and all softwares that I use, and even this did not help.


    Apart from that, every webpage loads. Only those, that are on my development server, don't. What did I do wrong?

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,411
    Blog Entries
    2

    Default Re: ERR_CONNECTION_REFUSED on intranet

    What kind of "web development server" are you running? -- A prepackaged configuration? Apache, nginx, node, something else?

    Has something been logged to your syslog? So, for instance immediately after a failure, does the following return something?
    Code:
    tail /var/log/messages
    Have you probed the port using something like telnet to verify the port is open and a service responds? Or, if the probe fails, then what is the message?

    Also, have you verified that the "web development server" is even running?

    TSU

  3. #3

    Default Re: ERR_CONNECTION_REFUSED on intranet

    The development server is a Vagrant solution running in VirtualBox and configured with PuPHPet. It runs Apache on Debian 7.5.

    /var/log/messages does not contain any errors.

    telnet www.awesome.dev 80 says:
    Code:
    Trying 192.168.56.101...
    telnet: connect to address 192.168.56.101: Connection refused
    However, there is an open port for SSH (6580):
    Code:
    Trying 192.168.56.101...
    Connected to www.awesome.dev.
    Escape character is '^]'.
    SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u2
    And yes, the server is running.

    By the way, I don't think that the problem is in the development server, because earlier, before upgrading the host to openSUSE 13.2, the server worked. What is more, in a Vagrant setup, the point is that it is pre-configured and works out of the box.

    Thank you for your help!

  4. #4

    Default Re: ERR_CONNECTION_REFUSED on intranet

    Maybe, is there a changelog for openSUSE 13.2 about network configuration changes available somewhere?

    Also, here is a list of my iptables rules. Does it contain inappropriate settings, which may break connection to intranet resources? Unfortunately I am quite dumb for iptables.

  5. #5
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,411
    Blog Entries
    2

    Default Re: ERR_CONNECTION_REFUSED on intranet

    When you use telnet to probe a port (to see whether it's open or not, and whether a service is behind it), you need to specify that port in the command, else you're just probing the default telnet port (which no one should ever use nowadays due to lack of security).

    Eg To probe a webserver for common HTTP and HTTPS ports,
    Code:
    telnet address 80
    Code:
    telnet address 443
    You're looking for something other than, for instance "connection refused"
    If an actual service (like a mailserver) exists, then you'll see something returned (like a mail server banner)
    A webserver service won't return a telnet probe with content, but you can follow up with a GET command if you actually want to see web content, but that usually isn't too different than connecting with a web browser (so is not commonly tried).

    TSU

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •