How to Configure HTTP Custom Using Different Payload Types (Full Step-by-Step Guide)
If you’ve already learned how to configure HTTP Custom using an SSH account, SNI host, and HTTP payload, this guide will take you to the next level.
In this tutorial, you’ll learn how to use other payload types including TLS/SSL and Reverse Payloads to get connected on different networks. This method can help you fix failed connections or boost your VPN performance depending on your region and provider.
What You’ll Need
- The HTTP Custom app installed on your Android device. Download from Play Store
- A working SSH account. Follow this guide:
Step 1: Generate Your SNI (Server Name Indication)
To generate an SNI Bug Host:
SNI Generator- Search for your country.
- Select it, and your SNI will be generated.
- Copy one of the provided SNIs.
Always use an SNI that matches your network provider and country to ensure compatibility.
Step 2: Create or Get Your SSH Account
Follow this guide:
Step 3: Generate Your Payloads
Use the Payload Generator:
Payload Generator- Under SNI Bug Host, paste the SNI from Step 1.
- Under Server Name, paste the server from Step 2.
- The generator will display these payload types:
- HTTP Payload
- TLS/SSL Payload
- Reverse Payload
This time, focus on TLS/SSL and Reverse payloads if standard HTTP fails in your region.
Step 4: Configure HTTP Custom
Open HTTP Custom and under ip:port@username:pass, replace with:
snihost:443@username:password
Step 5: Apply the Payload and SNI
- Open the navigation menu → Payload.
- Paste one of the payloads (start with the TLS/SSL payload).
Then:
- Open the navigation menu → SNI.
- Paste your servername from Step 2 and click Apply.
Step 6: Test Your Connection
- If the app shows an error, stop and switch to another payload.
- Try connecting again.
- If you see “200 OK” in the log, your SNI is active and working.
- If it still doesn’t connect, try using V2Ray in HTTP Custom.
Step 7: When Your SNI Is an IP Address
In some cases, especially for certain networks, your SNI might appear as an IP address instead of a domain name.
SNI: 104.16.181.84 Payload: [payload code] Proxy: 172.66.0.251
Don’t worry — these SNIs can also work. In the next tutorial, we’ll show how to configure HTTP Custom with IP-based SNIs and proxy servers.
Troubleshooting Tips
- Double-check that your SSH account is active.
- Ensure port 443 matches your server configuration.
- Try different payloads if you get repeated connection errors.
- If you see “200 OK” but can’t browse, switch payload methods or restart the app.
Final Thoughts
Getting a stable connection on HTTP Custom can take a few tries — but once you find the right combination of SNI, payload, and SSH server, you’ll connect smoothly.
If you found this guide helpful, please share it with others. And don’t forget to subscribe to our YouTube channel: youtube.com/@snihost for more tutorials like this.