Hey, I’ve noticed that when I run my proxies (host:port:user
) on the OB2 web version, they sometimes work but occasionally fail on certain configs, while they consistently work on the CLI version.
It’s pretty strange. I usually prefer using the web version, but this issue has forced me to switch to the CLI version for now.
Edit:
I noticed that a configuration that used to work perfectly is now causing bans. The issue turned out to be the missing Content-Length header.
I originally thought this header wasn’t always necessary, but adding it made everything work again, including on the web version. I’m still a bit confused about why this happened.
The proxies worked fine with the CLI version, but not with the web version until this change.
Now, everything is back to normal. Can you help me understand what might have caused the issue?
It’s likely an issue with your proxy provider. The content length will be added automatically by OB2, so you don’t need to add it manually. However, if you choose to add it manually, make sure you don’t make any mistakes. If the content length doesn’t match properly, OB2 won’t make the request and it will be denied. It’s better to leave that header as OB2 will manage it
I wasn’t aware that OpenBullet automatically adds the Content-Length header now. I just learned something new, haha.
Still, after I manually added it, the issue was resolved. I read online that the requests couldn’t go through because the Content-Length header was missing, just like you mentioned earlier. Maybe OpenBullet didn’t add it this time, or the value didn’t match. So, I used the Content-Length block and included the header with the correct value for the post data, and that fixed the issue. Although, I’m still getting some banned responses, which I guess is normal due to the target’s rate-limiting and other protective mechanisms.
By the way, do you have any explanation for why this might have happened? Or do you think someone should check it out?
btw.
I don’t think it’s the proxy either — I’ve already checked, and it’s working fine. I normally don’t have any issues with it. Plus, that wouldn’t explain why everything works in the OpenBullet 2 CLI version but not in the web version. Any thoughts on why that might be happening?
I don’t know maybe Ruri will explain better, my guess was it happened due to tls handshake, the site you are working on has waf and is protected from OB2 TLS fingerprint. There are many factors if you using the windows os version also matter here. if you want to fix open the issue on Git Hub with more detail.
Hello, which version of OB2 are you using for web and CLI? Maybe the CLI was an older release and it worked due to some change that happened in the meantime, but it still sounds a bit weird, since both versions use the same shared library (RuriLib) and I didn’t change anything in the Http module for a long time. Are you using both from the same PC/OS?
Yes, it was the same OS, and I always use the latest versions on both devices. However, I had to manually add the Content-Length header to the headers because it wasn’t added automatically. After doing that, it worked again.