Popular antidetect browser in the Chinese market with Selenium automation support. Connect KnoxProxy to Lalicat for scalable multi-account operations with geo-targeted proxies and automated profile launching.
Launch the Lalicat application and log in to your account.
Click "Add Profile" from the main dashboard.
In the profile editor, click the "Proxy Setting" tab.
Select "HTTP Proxy" or "Socks5 Proxy" from the type dropdown.
Fill in your KnoxProxy gateway credentials.
Proxy Host: gw.knoxproxy.com
Proxy Port: 7000 (HTTP) or 7001 (SOCKS5)
Proxy Account: your_username-country-jp
Proxy Password: your_passwordClick "Test Proxy" to verify, then click "Save" to store the profile.
from selenium import webdriver
# Lalicat exposes a local Selenium port per profile
# After launching a profile, connect via its debug port
options = webdriver.ChromeOptions()
options.debugger_address = "127.0.0.1:9222" # Lalicat debug port
driver = webdriver.Chrome(options=options)
driver.get("https://httpbin.org/ip")
print(driver.page_source)
driver.quit()Set -session-{profileId} in the proxy username for sticky sessions. Without a session flag, each profile launch receives a new IP.
| Problem | Fix |
|---|---|
| Proxy test shows "Connection failed" | Allow outbound traffic to gw.knoxproxy.com on ports 7000 and 7001 in your firewall. |
| Selenium cannot connect to profile | Launch the profile in Lalicat first, then use the correct local debug port shown in the profile list. |
USER-country-de-city-berlin-session-profile07Order matters -- geo flags before the session flag. The session name is free text; use the profile ID so the mapping is self-documenting. Password stays as issued; no flags belong there. HTTP on :7000, SOCKS5 on :7001, same credentials.
Yes. Set KnoxProxy as the profile proxy in Lalicat's Proxy Setting tab, launch the profile, then point Selenium's ChromeOptions.debugger_address at the local debug port shown in the profile list, typically 127.0.0.1:9222. Selenium then drives the already-proxied browser session instead of launching its own separate instance.
Yes. Use the Lalicat API to create profiles programmatically, passing your KnoxProxy host, port, account, and password into each profile's proxy fields the same way you would in the GUI. Add a different -country-{cc} or -session-{profileId} suffix per profile so bulk-created profiles land on distinct geo-targeted exit IPs.
HTTP on port 7000 works for most use cases and is the simpler default when setting up a Lalicat profile. Choose SOCKS5 on port 7001 instead if your workflow needs UDP support or lower-level protocol handling that a plain HTTP proxy cannot provide, then select Socks5 Proxy from the type dropdown.
Yes. Set -country-{cc} in each profile's proxy account field, for example your_username-country-jp for Japan, in the Proxy Setting tab shown during profile creation. Every profile then routes through the same gw.knoxproxy.com gateway but exits from its own targeted country, so no two profiles need to share the same location.
Rotating residential proxies -- 3 minutes setup, instant activation, 14-day money-back guarantee.