Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed network typebot issue #1984

Open
Blessed-Knight opened this issue Jan 31, 2025 · 3 comments
Open

Closed network typebot issue #1984

Blessed-Knight opened this issue Jan 31, 2025 · 3 comments

Comments

@Blessed-Knight
Copy link

I use a closed network on which an SMTP server is deployed, which is included in the config. When trying to work on this closed network, the containers try to gain access to the open network, which breaks the functionality of the bots. Are there ways to solve this problem?

@baptisteArno
Copy link
Owner

the containers try to gain access to the open network

Can you explain that? what makes you think this?

@Blessed-Knight
Copy link
Author

When using a closed network, the invitation to the SMTP server did not arrive. On an open network, we were able to track an access to the following address on port 433:

  1. 185.199.108.133
  2. 185.199.109.133
  3. 185.199.110.133
  4. 185.199.111.133
    Thanks to this, solutions have come for new users.

@baptisteArno
Copy link
Owner

Sorry I don't understand. If you provide SMTP creds that point to a local server, it should never communicate with the outside 🤔

I am not sure how it relates to Typebot too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants