I am currently having an issue with my ejabberd server I've set up recently: Any client is unable to connect to the server. Whether it is Psi or a sample code from the net, all produce an error when it comes to connecting, even though both is located on my computer, so no network issues can be the reason.
I have so far tried to bind the listener to a different port, and also checked the values in the ejabberd.yml. However, I was not able to find a sulution for my problem.
The service log of the server was not conspicious either:
2015-12-28 18:16:29.923 [info] <0.7.0> Application oauth2 started on node ejabberd#localhost
2015-12-28 18:16:29.938 [info] <0.449.0>#ejabberd_listener:listen_tcp:189 Reusing listening port for {5222,{0,0,0,0},tcp}
2015-12-28 18:16:29.938 [info] <0.450.0>#ejabberd_listener:listen_tcp:189 Reusing listening port for {5269,{0,0,0,0},tcp}
2015-12-28 18:16:29.938 [info] <0.451.0>#ejabberd_listener:listen_tcp:189 Reusing listening port for {5280,{0,0,0,0},tcp}
2015-12-28 18:16:29.938 [info] <0.37.0>#ejabberd_app:start:75 ejabberd 15.11 is started in the node ejabberd#localhost
2015-12-28 18:16:29.938 [info] <0.7.0> Application ejabberd started on node ejabberd#localhost
Did I do something wrong when entering the parameters? Or is this a problem of configuration? My first idea was that my anti-virus avast might be blocking some of the traffic, but i couldn't find anything on the web about that.
Attached you can find screenshots of psi and the server-ui.
The host name is pc-michi
With this link you can view my .yml file:
http://workupload.com/file/rQoLIf4Y
Could you please tell me what goes wrong here?
Thanks in advance :)
It looks like basic networking configuration issue. Psi client is not able to connect to the server. There may be multiple reasons:
Firewall blocking port.
Name of the machine you use to connect to cannot be resolve to proper IP address.
You should try connecting on that host on port 5222 from command-line, for example with telnet to check that you can open a TCP socket properly.
Related
after a change in the IP, our server has stopped working. Only the host can connect to the server. we already tried Whitelisting Java and the port, restarted the router, reinstalling java, and even made another complete server. It just stopped working. does anyone have a solution to this?
Have you port forwarded your router correctly?
If not then only connections from your LAN network can connect to the server.
Good day
I'm completely new to ejabber. I have installed ejabber on debian (on virtual machine) but when I tried to check it with localhost (http://localhost:5280/admin) mozilla responded with the announcement "the connection was interrupted". I checked logs of ejabber and it had multiple lines of accepting connection on port 5280.
2018-06-02 14:27:50.526 [info] <0.491.0>#ejabberd_listener:accept:333 (#Port<0.12507>) Accepted connection ::1:32948 -> ::1:5280
2018-06-02 14:27:50.534 [info] <0.635.0>#ejabberd_http:init:163 started: {fast_tls,{tlssock,#Port<0.12507>,#Port<0.12508>}}
What is the reason of it and how could I get past this issue?
You have configured ejabberd to use TLS on port 5280 (see: tlssock in your logs), but you are using plain HTTP when trying to connect to it (http://localhost:5280).
You should use HTTPS to connect to it, assuming your cert is properly configured in ejabberd.
I have configured jetty-maven-plugin in my eclipse Mars and I can run the server using jetty start and stop goals. I can able to access the website using http://localhost:8080/myapp but not using local IP address(i.e., http://192.168.0.5:8080/myapp) from my own computer or other computers connected in the same network via LAN and Wi-Fi.
As mentioned as a solution in these posts,
how to make jetty server accessible from LAN?
Configuring Jetty to accept connections from all hosts
I configured the server host to 0.0.0.0 from localhost to listen on all hosts. With this setting I can see on server start log,
INFO:oejs.AbstractConnector:Started SelectChannelConnector#0.0.0.0:8080
and it works only on http://localhost:8080 but it's not accessible from http://192.168.0.5:8080.
I also tried running that if the interface is accessible using the Networks Interface Listing as mentioned in this comment. and I got,
Display name: NETGEAR WNA1000M N150 Wireless USB Micro Adapter
Name: wlan4
InetAddress: /192.168.0.5
I also tried turning off my Windows Firewall/antivirus but din't help. My jetty version is <jetty.version>9.3.0.M1</jetty.version> and JDK 1.7. What could be the problem? Any help is appreciated.
McAfee Endpoint Security was the culprit here. It was blocking the requests with IP addresses from my very own computer. Turned off the firewall inside the Antivirus and I was able to access the site with http://192.168.0.5:8080/mysite from the browser and other devices connected through the network.
Sometimes some other program opens your port on external address before you do that with Jetty. It will receive all traffic instead. On Windows you will not know it if you reuse port (that is Jetty's default behavior). Check with netstat -ano what is the IP of the process that is indeed listening on 0.0.0.0:8080. Verify if it is your Jetty process only.
Then try connecting with telnet or netcat and see if you can open the connection and what is the response.
Hi Can someone plese help me to solve the following issue.
I have started my websphere server and it is using the following ports
TCP_1 is listening on host * (IPv6) port 9061.
TCP_2 is listening on host * (IPv6) port 9081.
TCP Channel TCP_4 is listening on host * (IPv6) port 9444.
When I stoped and started my server again I'm getting message saying that
TCP Channel TCP_3 initialization failed. The socket bind failed for host * and port 9043. The port may already be in use.
Can anyone advise me why it is not stopping automatically
Aprreciate your help on this. Thanks in advance
The specific problem is well known and is usually caused by the fact that there are still TCP connections from the previous WAS process (i.e. before restarting it) using the port.
Eventually the port will be released and the new WAS process will be able to bind it.
One way to overcome this annoyance is to set the soReuseAddr property to 1 in the TCP transport channel.
9043 is the Admin Console secure port. Do you have a dmgr running on this server in addition to a stand alone app server?
All connection attempts on RhodeCode on CentOS 6.3 are refused except from localhost.
Note that iptables is not running, and I am only trying to visit the web interface.
I have googled the exact error message below and looked around SO. I have yet to find a solution.
abort: error: No connection could be made because the target machine actively refused it
If the firewall is down, and I am not trying to modify any repository, what else is preventing me from connecting? EDIT: See #5 below. Not sure how to address it yet.
Things tried and other info
Using localhost, 127.0.0.1 and hostname in production.ini
service iptables stop
Connected over HTTP successfully. In other words, connections are accepted outside RhodeCode.
Made sure no authentication methods were enabled or configured in production.ini
Although the server accepts connections on localhost, netstat -l does not show that port 5000 is listening. Port 5000 is set in production.ini and ps uax | grep paster confirms the server is running. No other software tries to grab port 5000.
Ok, apparently I have been misunderstanding the host configuration. I was running on the assumption that host should be set to 127.0.0.1 or localhost in production.ini for RhodeCode to know what host to look for for another service. This was a faulty presumption on my part, since I am used to pointing web applications to local systems to look for databases.
It turns out that host binds the application to a specific address for access, meaning that it RhodeCode was supposed to only respond to local requests, regardless of what other system policies say. The setup docs did not make this clear because it did not specify that external connections would be refused. All it said was:
This command [paster serve] runs the RhodeCode server. The web app should be available at the 127.0.0.1:5000. This ip and port is configurable via the production.ini file created in previous step
The problem was fixed by binding RhodeCode to 0.0.0.0, which opened it to outside connections. Kudos to Łukasz Balcerzak for pointing this out in the RC support google group.