Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hello guys, today i just faced out that my MailHog (mailcatcher container) does not work more proper

Options
giovanni.piemontese
giovanni.piemontese Technical Lead @ Löffelhardt Spryker Solution Partner Posts: 871 🧑🏻‍🚀 - Cadet
edited July 2020 in Docker

Hello guys,
today i just faced out that my MailHog (mailcatcher container) does not work more properly..

The WebUi of MailHog is working but the websocket is always disconnected.. I've seen the following error in browser console:
WebSocket connection to wss://<my-domain>/api/v2/websocket failed: Unexpected response code: 400

Has anyone an idea?

Comments

  • sprymiker
    sprymiker Cloud Platform Architect Sprykee Posts: 781 🧑🏻‍🚀 - Cadet
    Options

    What is docker/sdk version?

  • giovanni.piemontese
    giovanni.piemontese Technical Lead @ Löffelhardt Spryker Solution Partner Posts: 871 🧑🏻‍🚀 - Cadet
    Options

    Hi Mike,
    i have last week on Friday updated on last master... I think is 1.15

  • UKHR9UN00
    UKHR9UN00 Posts: 70 🧑🏻‍🚀 - Cadet
    edited July 2020
    Options

    Hi Giovanni,
    I'm not sure if it helps with your particular problem, but we often have issues with MailHog if there were too many emails.
    In that case we have to "delete all messages" - even if you don't see any messages in the UI. After that mailhog receives mails again.

  • sprymiker
    sprymiker Cloud Platform Architect Sprykee Posts: 781 🧑🏻‍🚀 - Cadet
    Options

    If @UKHR9UN00’s advice does not help, it would be a bug.

    We changed FE architecture. However I wonder what would be wrong as the proxy pass rules are the same.

  • giovanni.piemontese
    giovanni.piemontese Technical Lead @ Löffelhardt Spryker Solution Partner Posts: 871 🧑🏻‍🚀 - Cadet
    Options

    @ULYHPR789 no. It does not help
    @UKHR9UN00 thank u for your tip

  • sprymiker
    sprymiker Cloud Platform Architect Sprykee Posts: 781 🧑🏻‍🚀 - Cadet
    Options
    Index: generator/src/templates/nginx/conf.d/gateway.default.conf.twig
    IDEA additional info:
    Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
    <+>UTF-8
    ===================================================================
    --- generator/src/templates/nginx/conf.d/gateway.default.conf.twig  (revision ec4591269d568e3e27fad1ddfe72c908bd9d7884)
    +++ generator/src/templates/nginx/conf.d/gateway.default.conf.twig  (date 1594158415741)
    @@ -4,6 +4,11 @@
     proxy_http_version 1.1;
     server_names_hash_bucket_size 128;
    
    +map $http_upgrade $connection_upgrade {
    +    default upgrade;
    +    ''      close;
    +}
    +
     map $cookie_XDEBUG_SESSION $xdebug_mode {
         ""      "";
         default "_xdebug";
    Index: generator/src/templates/nginx/http/gateway/server.conf.twig
    IDEA additional info:
    Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
    <+>UTF-8
    ===================================================================
    --- generator/src/templates/nginx/http/gateway/server.conf.twig (revision ec4591269d568e3e27fad1ddfe72c908bd9d7884)
    +++ generator/src/templates/nginx/http/gateway/server.conf.twig (date 1594158501759)
    @@ -11,11 +11,15 @@
         include /etc/nginx/vhost.d/ssl.default.conf;
     {% endif %}
    
    +{% block locations %}
         location / {
             proxy_set_header Host $host;
             proxy_set_header X-Real-IP $remote_addr;
    +        proxy_set_header Upgrade $http_upgrade;
    +        proxy_set_header Connection $connection_upgrade;
             proxy_pass http://{% block upstream %}{{ upstream }}{% endblock upstream %};
         }
    +{% endblock locations %}
    
         error_page 497 {{ desiredProtocol }}://$host{{ isPortCustom ? ':' ~ port : '' }}$request_uri;
     }
    

    @UL65CH0MC Would this patch help, please, try.

  • sprymiker
    sprymiker Cloud Platform Architect Sprykee Posts: 781 🧑🏻‍🚀 - Cadet
    Options

    I’ve checked and it works for me as well with this patch.

  • sprymiker
    sprymiker Cloud Platform Architect Sprykee Posts: 781 🧑🏻‍🚀 - Cadet
    Options

    I will create a ticket and we will release the fix the next week.

    Thank you for reporting this.

  • giovanni.piemontese
    giovanni.piemontese Technical Lead @ Löffelhardt Spryker Solution Partner Posts: 871 🧑🏻‍🚀 - Cadet
    Options

    Hi mike.. ok thanks.
    sorry but i cannot yesterday test and was planned for today..

    Thank u very much!