Don't work bucket replication

[justc0de-it]

Describe the bug
When I try start bucket replication get error

Connection error for bucket: warp-test, access key: a05AhNoov4 quahC2daSahth, error: failed
to dispatch bucket exists for bucket: warp-test
error:DispatchFailure { source: ConnectorError {
kind: lo, source:
hyper_util::client::legacy::Error(Connect,
ConnectError " dns error", Custom {
kind: Uncategorized, error: " failed to lookup address information: Name does not resolve" })), connection: Unknown }}

To Reproduce
Steps to reproduce the behavior:

1. Go to bucket replication setting
2. Add rules
3. Push Add
4. See error

Expected behavior
From server via CLI domain is resolved.

Screenshots

Desktop (please complete the following information):

• OS: MacOS
• Browser Safari
• Version 26.3

Additional context
RustFS run as systemd-service on Ubuntu 24.04

[loverustfs]

Hello,

What are your steps & version?

[justc0de-it]

1. Created an account, policy, and token for replication.
2. Created a test bucket on both servers with versioning enabled.
3. Go to the bucket settings menu and select Replication.
4. Fill in the fields as shown in the screenshot.

5. After clicking the Add button, I get the error shown in the screenshot.

6. RustFS Version

root@s3-prod:~# rustfs --version
rustfs 1.0.0-alpha.79
build time   : 2026-01-07 13:08:14 +00:00
build profile: release
build os     : linux-x86_64
rust version : rustc 1.92.0 (ded5c06cf 2025-12-08)
rust channel : stable-x86_64-unknown-linux-gnu
git branch   : 
git commit   : a95e549430851f3c34ee4cc8dd7be60aa200e8c4
git tag      : 1.0.0-alpha.79
git status   :

7. RustFS Settings

RUSTFS_ACCESS_KEY=USER
RUSTFS_SECRET_KEY=PASS
RUSTFS_VOLUMES="/data/rustfs0 /data/rustfs1 /data/rustfs2 /data/rustfs3 /data/rustfs4 /data/rustfs5"
RUSTFS_ADDRESS=":9000"
RUSTFS_CONSOLE_ENABLE=true
RUST_LOG=error
RUSTFS_OBS_LOG_DIRECTORY="/var/logs/rustfs/"

[evanofslack]

@justc0de-it try to setup without the https:// in your endpoint for target bucket. If you need TLS then check "Use TLS" option.

[loverustfs]

@justc0de-it try to setup without the https:// in your endpoint for target bucket. If you need TLS then check "Use TLS" option.

Yes, that is the correct answer.

Is it possible to add reminders and filters to the front end? @cxymds

[cxymds]

@justc0de-it try to setup without the https:// in your endpoint for target bucket. If you need TLS then check "Use TLS" option.

Yes, that is the correct answer.

Is it possible to add reminders and filters to the front end? @cxymds

Sure, I’ll add a friendly prompt.

[cxymds]

Set the default protocol to HTTP, and automatically switch to HTTPS when TLS is enabled.

[Tydragon00]

same issue

[justc0de-it]

Set the default protocol to HTTP, and automatically switch to HTTPS when TLS is enabled.

I use http and https protocol. Try use: http://s3.domain, https://s3.domain and s3.domain. All this variants don't work.

With http://s3.domain and s3.domain got error: "bucket don't exist" 🤷‍♂️ And this solution look strange: clients may use http -> https redirect for their domains, for example.

Throw linux network utilities check network request: if use https protocol RustFS try connect to another instance throw bucketname.s3.domain. Don't matter what settings use in configuration - use s3.domain/bucketname or bucketname.s3.domain (in my configuration use default link path).