[GH-ISSUE #35] Question on domain to use OBFS #29

Closed
opened 2026-02-26 12:33:46 +03:00 by kerem · 3 comments
Owner

Originally created by @yagigain on GitHub (Jun 25, 2019).
Original GitHub issue: https://github.com/cbeuw/Cloak/issues/35

Quick question, I think I know the answer.

Would it be better to use a domain for the OBFS that resolves to the same IP used for the SS server ?

The default in the config is bing, but this wouldn't work as well as a domain resolving to SS IP ?

Or doesn't it matter with Cloak ?

Originally created by @yagigain on GitHub (Jun 25, 2019). Original GitHub issue: https://github.com/cbeuw/Cloak/issues/35 Quick question, I think I know the answer. Would it be better to use a domain for the OBFS that resolves to the same IP used for the SS server ? The default in the config is bing, but this wouldn't work as well as a domain resolving to SS IP ? Or doesn't it matter with Cloak ?
kerem closed this issue 2026-02-26 12:33:46 +03:00
Author
Owner

@cbeuw commented on GitHub (Jun 25, 2019):

Ideally the domain name should resolve to the WebServerAddr field in ck-server configuration. But this doesn't affect the functionalities of Cloak.

<!-- gh-comment-id:505323189 --> @cbeuw commented on GitHub (Jun 25, 2019): Ideally the domain name should resolve to the `WebServerAddr` field in ck-server configuration. But this doesn't affect the functionalities of Cloak.
Author
Owner

@yagigain commented on GitHub (Jun 25, 2019):

ok thanks ... but it dosn't help to have it on the same IP as "server' in config.json (for SS) ? Like with V2Ray you have the webserver on the IP of SS using reverse proxy to share the port.

<!-- gh-comment-id:505331283 --> @yagigain commented on GitHub (Jun 25, 2019): ok thanks ... but it dosn't help to have it on the same IP as "server' in config.json (for SS) ? Like with V2Ray you have the webserver on the IP of SS using reverse proxy to share the port.
Author
Owner

@cbeuw commented on GitHub (Jun 25, 2019):

If you are running a webserver on the host, then yes you can leave it as the address of your webserver. But note it should be a localhost address. If you leave it as your public IP a.b.c.d:443, then ck-server will redirect the traffic back to ck-server causing an infinite loop.

<!-- gh-comment-id:505333774 --> @cbeuw commented on GitHub (Jun 25, 2019): If you are running a webserver on the host, then yes you can leave it as the address of your webserver. But note it should be a localhost address. If you leave it as your public IP a.b.c.d:443, then ck-server will redirect the traffic back to ck-server causing an infinite loop.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Cloak#29
No description provided.