Important: If you are a Zammad Support or hosted customer and experience a technical issue, please refer to: support@zammad.com using your zammad-hostname / or company contract.
Used Zammad version: 2.7
Used Zammad installation source: (source, package, …) RPM Package
Operating system: Centos 7
Browser + version: Chrome 71/Firefox
Expected behavior:
Chat Window Opens
Actual behavior:
Chat Window fails to open
Steps to reproduce the behavior:
Load the page…
I am receiving this error in the debug output of the java script. I don’t believe the WS on port 6042 should be exposed to the internet since it is bound to the localhost only? I did need to update the nginx config to not use localhost hostname but 127.0.0.1 as it seems that the below do not bind to a IPv6 local address on the host and was causing some internal connection timeouts trying to connect to [::1]:6042 The website is being served using HTTPS only. I also picked up that agents do not see any options to choose which chatID they would like to receive chats on… it just displays the form headers but with no content.
upstream zammad-railsserver {
server 127.0.0.1:3000;
}
upstream zammad-websocket {
server 127.0.0.1:6042;
}
Java Error:
io debug || onMessage [{“event”:“error”,“data”:{“error”:“No connection pool with ‘primary’ found.”,“payload”:{“event”:“chat_status_customer”,“data”:{“session_id”:null,“url”:“https://www.website.com/","chat_id”:1}}}}]
chat debug || ws:onmessage
1. Object
1. data: {error: "No connection pool with 'primary' found.", payload: {…}}
2. event: "error"
3. __proto__: Object
io debug || onMessage [{“event”:“error”,“data”:{“error”:“No connection pool with ‘primary’ found.”,“payload”:{“event”:“chat_status_customer”,“data”:{“session_id”:null,“url”:“http://myurl/","chat_id”:1}}}}]
Just giving the ideia, similar to zendesk for example, the client can open the chat box, place the email and text for question. At the moment, the current chat, requires the Customer to open and wait in line.