Used Zammad installation type: (source, package, docker-compose, …)
Operating system: ubuntu 20.0.4
I want to use Zammad as a ticketing system because we have a small number of users, so I haven’t used NGINX. When I use the development mode and start with dev:https using a self-signed certificate, and then open the port for external access on the server, I keep getting the error “The connection to the server is lost” when using the mobile version. I can’t solve it. Do I need to configure NGINX?
I am surprised at such a reaction.
I only reported that there is the same problem in another thread.
I think it’s inappropriate to react like this when you’ve only asked the entire community politely.
So far I couldn’t read anywhere why it doesn’t work.
If it doesn’t work in the Docker / Nginx environment, it also shows that other users here have the problem. If there is a solution, it would be nice to hear about it. If there is none as well.
Sorry, it was not my intention that anyone here should feel that they had stepped on someone’s toes
Yes, I have reviewed this article before, but my NGINX didn’t start properly, so I didn’t use NGINX. I deployed it through the internal network. I noticed that the reply button and the ticket details page cannot be accessed. I’m wondering if this issue is related to certain configurations.
Thank you very much for your reply~ My issue is that when I access the system from my computer (e.g., 192.168.10.*) using HTTPS with a locally signed SSL certificate, it seems to be more stable. I’m not sure if it’s because the computer’s processor has better parsing capabilities. However, when I access it on my phone through the IP on the same Wi-Fi, it seems less stable, even though the network is still functional (I can use TikTok smoothly). Are there any logs I can check to troubleshoot this issue?
I see, it seems like the issue might be related to an ESL and SSL component. Unfortunately, since I started the system using the source code, it seems like the setup might be slightly different.
I also noticed that the issue only appears suddenly, which significantly affects the user experience. It seems that the upper part of the page loads without issues, but the reply button at the bottom never works, and the form details page also fails to load. This is quite critical.
I also noticed that the data for this request seems to come later. I’m wondering if it would be better to handle it asynchronously. A single request might become too large, especially if there are images in the ticket information.
Maybe you can summarize what is you current problem. I can not really follow inside this thread.
But in general, when the cable connection is working in general, we didn’t saw problems with unexpected disconnects.
Ah, I’m really sorry to hear that you’re facing this issue. To clarify the problem: I’m using a self-signed certificate to start the service with pnpm run dev:https, and I’m accessing it via https://192.168.10.29:3000. However, when I click on the ticket page, it keeps showing “connection lost” and doesn’t work properly.
When I try accessing https://192.168.10.29:3000 on my mobile phone and repeatedly test by clicking on the page, the same issue occurs. It keeps showing “connection lost.”
Please do not access Zammads Puma directly without proxy in between.
If your cable / websocket connection in general is unstable, you will have to find the reasoning for this.
This is not a classic Zammad issue but might be caused by e.g. firewalls etc.
The websocket connection is vital for the mobile view and upcoming desktop view:
Is there a recommended way to compile from the source code? Or any documentation? I want to compile from the source, such as using Vite, and then deploy both the frontend and backend on my server for running.
I’ll try using NGINX as a proxy, but it seems that the NGINX configuration I wrote isn’t working. It looks like only either NGINX or the Puma server can specify the SSL certificate, so the issue might be related to how I installed the source code.
