Skip to content
Snippets Groups Projects

ws2p-public doesn't work if ws2p-private is disabled

    • Open Issue created by Éloïs @librelois

    The ws2p endpoint is not published if ws2p-private is disabled

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Éloïs
      Éloïs @librelois ·
      Author Owner

      Please, keep this issue open. My commit has not solved the problem, we would have to rewrite ws2p in depth so that it can work in public mode only. In any case it is possible to work in public mode only by setting ws2p-max-private to zero so it is not a priority need.

    • Cédric Moreau
      Cédric Moreau @c-geek ·
      Owner

      we would have to rewrite ws2p in depth so that it can work in public mode only

      Nah... the issue is certainly simple to identify and fix.

    • Cédric Moreau
      Cédric Moreau @c-geek ·
      Owner

      If you want I can have a look. Jus tell me.

    • Cédric Moreau
      Cédric Moreau @c-geek ·
      Owner

      From what I observed with an UPnP configuration, ws2p-public well publishes the WS2P endpoint even if ws2p-private is disabled.

      However, there is a concurrency with other services and sometimes the endpoint is not immediately published.

      Let's delay this issue to another release, it is not critical at all.

    • Éloïs mentioned in commit 1ea16cd3

      mentioned in commit 1ea16cd3

    • Éloïs unassigned @librelois

      unassigned @librelois

    Please register or sign in to reply