Messenger problem - SOLVED
Hello Una team,
I installed messenger and it's server.
But I am having the same problem that we were having here at Una site before the messenger updates.
Please see the video file as it's difficult to explain it written.
What do you think Alexey ?
-
- · Peter
- ·
I had the same issues. What is your ''Server URL for messenger'' in studio/messenger?
-
- · Cem
-
·
In reply to Peter
- ·
https://localhost:5797 (custom port no)
-
- · Peter
- ·
the default setting should be
https: // yourdomain:5000
-
- · Cem
-
·
In reply to Peter
- ·
Hi Peter I will try with that port now. Thanks :)
-
- · Peter
- ·
AlexT helped me out with this issue twice *gg
-
- · Cem
- ·
Peter it didnt change the behavior of the text box. Only if you click the name of the person or rewrite the name it allows to write the message.
-
- · Peter
- ·
ok cem, sorry, I cant help with this. I use a UNA hosted setup and all probs are solved by the guys...
-
- · Cem
-
·
In reply to Peter
- ·
Thanks a lot Peter lets see what will Alexey recommend .
-
-
·
Alexey
- ·
Hello Cem Bagdatli ,
Seems like problem with Server Url or with Port which is used for Jot Server. Please be sure that the port is opened, you may check it using windows command line or putty client.
You need type command format:
telnet
example:
telnet hekim.net 5000
The successful connection (port is opened) you will see blinking cursor on a blank screen. If the connection fails, troubleshoot the failed connection.
-
·
Alexey
-
- · Cem
- ·
# telnet hekim.net 5000
Connection to hekim.net:5000 - ok
Also stopping the firewall completely, is not changing the behavior -
- · Baloo
-
·
In reply to Cem
- ·
Someone had a similar problem here, it was a ssl certificate problem, you're on Cem side, it's the good one, and the path is coorect in the jotserver config settings?
-
- · Cem
-
·
In reply to Baloo
- ·
Tomorrow morning let me check once more the paths Baloo thanks.
-
-
·
Alexey
- ·
Hello Cem Bagdatli,
As far as I see from browser console on your site, connection is ok now and you may send messages, but Jot Server still doesn't allow to distribute messages between members because your site's IP is not included to allowed Ips list for the server. I mean seems like you have added site's IP to "domain" option of the server's config.json, but your site's IP is 127.0.0.1 and thus your are blocked.
Please add 127.0.0.1 IP to domain's list and restart the server and then everything should work fine.
-
·
Alexey
-
- · Cem
- ·
for https in UNA studio add your domain (of the certificates) and port in Server URL for messenger area like :
https://yourdomain.com:portno -
- · Jeremy
- ·
What about if its a different server running on the same network but doesn't have a url attached to it...only an internal ip? Would we enter https://internalip:portno like 10.10.10.10:5443 Or is this possible? I think it should be, however it isn't working for me as of now.
-
- · Cem
-
·
In reply to Jeremy
- ·
may be to try with a xxx.yourdomain.com subdomain in your hosts file mapping to the local ip Jeremy ?
-
- · Jeremy
- ·
It's not a sub. Its a completely different machine setup to run JotServer but only has an internal IP. I have used that IP and port number but connecting failed. Still think there is something blocking the port. Telnet fails also so...still looking at it
-
-
·
Alexey
-
·
In reply to Jeremy
- ·
Hello Jeremy,
Yes it should work with ip instead of domain.
-
·
Alexey
-
- · Jeremy
-
·
In reply to Alexey
- ·
Still think it's a port issue because even local IP isn't working and cannot telnet to the address yet either
-
-
·
Alexey
-
·
In reply to Jeremy
- ·
Yes, seems like port issue
-
·
Alexey
-
- · Asad Ur Rehman
- ·
-jailshell-4.1$ telnet domain(dot)com 5443
Trying x0.xx6.x2.xx6...
Connected to domain(dot)com.
Escape character is '^]'.
Connection closed by foreign host.
what is Connection closed by foreign host.?
and i am getting connecting.........
-
i started app forever
-jailshell-4.1$ forever -w --watchDirectory=/home3/xxxxxx/ROOT_domain(dot)com/ssl start app(dot)js
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info: Forever processing file: app(dot)js