Exposing a TCP port of a service

Questions and Answers Deployment
1

Hi there,

I have deployed a memcached service (from an official Docker Hub image), and I want to expose it publicly via a TCP port.

This is what I get from the console with the standard procedure:

image
image498×806 32.6 KB

I don’t fully understand the message and at this point I don’t know if this is troublesome.

Note that my cluster (OVH) is self-managed (so I guess this is not a local demo cluster) and I initially have a functional load balancer.

After the deployment, I can see that a new second load balancer has been created (via the OVH manager web interface). Is it supposed to happen?

Also, I am unable to reach my memcached service from the outside (using telnet). So I guess, something went wrong. :innocent:

Thank you in advance for your help!

Thomas @ Kirae

2

Hi @Kirae :wave: , thanks for opening a thread on your issue. Could you please share your web console service URL? Then we can check in more details :pray:

3

Hello @Kirae,

I’ve checked your questions with the team.

Your cluster is indeed self-managed, the blue text box is a bug on our end. We created a ticket to remove it.

The creation of the second load balancer is normal. You can check our documentation here, it states that:

Exposing publicly TCP/UDP ports requires to create a dedicated load balancer and it takes a few minutes before having it ready (~15 minutes). Note also that this has a direct impact on your cloud provider bill.

For the Memcached connection, can you give me more information?
On which env do you have the problem?
How do you try to connect to Memcached?

Regards,
Charles-Edouard

4

Hi,

Thank you for your replies.

Here is the URL:
https://console.qovery.com/organization/1e406795-87eb-46a3-bbff-1483439f8116/project/150cf9ee-2a30-4fe1-8d9d-21a9ac8e59f3/environment/5549d5d8-dda4-4b34-9e0d-c93656363133/application/18da3904-660c-4ddc-8c0e-0ce6efbd0f48/general

I guess its is safe to share it. Isn’t it? :sweat_smile:

I have tried to connect memcached using this method: How to Test Memcached Connectivity - KJBweb

I have tried it on other instances of memcached, and it works.

5

New development: the issue seems to come from the domains association

  1. I link my domain with the provided ****.cargo.rocks domain using a CNAME record (tested with a DNS checker).

At this stage, this is the message I get from the domain settings of my service :
image

  1. I try to connect to my service with my domain (via telnet). It fails.

  2. I try to connect to my service with the pXXXX-***.cargo.rocks domain, and it works.

7

Hello @Kirae,

Don’t worry, sending URLs is fine, it allows us to check your configuration.

Your Memcached works for me too on the cargo.rocks domain.

Can you send me a private message with your domain so I can check your configuration?

Regards,
Charles-Edouard

9

This topic was automatically closed after 12 hours. New replies are no longer allowed.