• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. Igcorreia

    Resolved Websockets not working in Docker

    @Kaspar it only works with this manual step.
  2. Igcorreia

    Resolved Websockets not working in Docker

    Hey, every docker image has a documentation page. There, I have included the reference of the volume for you. The names of the fields have changed but the implementation is the same: Container (precisely this): /baserow/data/ Host (here is your server; please customize the domain)...
  3. Igcorreia

    Resolved Websockets not working in Docker

    Hey, team, once again, I had to use the same trick these are my steps:
  4. Igcorreia

    Resolved Websockets not working in Docker

    @Kaspar, I think I manage to make it work. I am trying again for the second time and see if I can replicate it.
  5. Igcorreia

    Resolved Websockets not working in Docker

    @Kaspar your suggestion is not possible. We cannot use the "location /" inside the apache and NGINX. I have 20 Plesk servers and I never manage to use "location /". Any suggestion? I am still trying your suggestion....
  6. Igcorreia

    Resolved Websockets not working in Docker

    I have tried Nocodb. Same thing
  7. Igcorreia

    Resolved Websockets not working in Docker

    @deno gave it another go, but no luck. I will try using apache, Installing Baserow behind Apache // Baserow and we need to add the ports and urls.
  8. Igcorreia

    Resolved Websockets not working in Docker

    I need help please. There is not easy tutorial to follow. And I think the Docker Extension is adding the code on bullet number 3 from the image.
  9. Igcorreia

    Resolved Websockets not working in Docker

    @Peter Debik, I love your idea. But I have downloaded all of the vhosts default files and I can't find where that line of code should be edit. And I think the Docker Extension is making an override. Is that possible?
  10. Igcorreia

    Resolved Websockets not working in Docker

    @Peter Debik and @deno I think I found a solution, but I need to hack the nginx.conf file inside the /system/domain/conf folder. @Peter Debik what is the correct way to add 3 rules to the following: Is there a way to add it in the domain settings without accessing the server? Plesk does...
  11. Igcorreia

    Resolved Websockets not working in Docker

    @Peter Debik, your intention was only to know about lots of users not actually help me, correct? If that is the case can you please let me know, so I can find another way to help myself?
  12. Igcorreia

    Resolved Websockets not working in Docker

    @Peter Debik, thanks for reaching out. We just need an example of what configuration we need to do on a domain that would enable WebSockets. The communities are N8N, Baserow, UptimeKuma, and a few more. All of this software doesn't work on Plesk, and this creates a problem for a lot of users...
  13. Igcorreia

    Resolved Websockets not working in Docker

    Hey Plesk team, could you please create a tutorial about setting up a docker container with an app that uses WebSocket? It looks like a lot of people are requesting this. I am always reached by the community because nobody can. Here is another ticket just about this. Can you please install the...
Back
Top