search

ghostery / broken-page-reports

7 stars 3 forks source link

rumble.com #757

Open AdamGhst opened 3 weeks ago

AdamGhst commented 3 weeks ago

DO NOT include personal information. We're not responsible for personal information leakage in the report.

Website URLs

Please, list the website URLs having the issue in the following code block to prevent the potential leak of personal information.

rumble.com

Description

Describe your issue simple as possible. You'll need to describe how to reproduce the issue later.

Chat functions do not load and are not visible. Msg from user: "This is the case regardless of troubleshooting mode or not. The chat works in standalone FF and it works in any chrome browser I've tried, such as Brave, or whatever. I'm still trying to figure out how to disable singular filters in the filter list. Maybe that's not a possibility. IDK, but I think I could figure out which filter to disable if I can figure out how to do that."
Screenshots > Note that uploading any kind of artifacts via GitHub can be accessed without authentication. > > https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files Paste or upload your screenshots here:

Steps to reproduce

Writing clear reproduction steps and environment helps us to recognize and identify the issue faster.

unable to reproduce.

Environments

Writing your environments detailed helps us to recognize and identify the issue faster.

If you're using Safari, you can replace the browser version with the OS version. Please, write in numbers.

I used GhosteryPrivateBrowser same as user. For me everything works well (MacOS) User is is on LINUX UBUNTU

If you have other extensions installed, please list them below. This is not a necessary step but multiple extensions running in the same site may cause conflicts.

Other details

OGHersch commented 3 weeks ago

To clarify. I'm using ghostery privacy browser with Linux Ubuntu. When I use standalone FF, the chat works. When I use a Chrome browser, the chat works. When I use ghostery in troubleshooting mode, with any extensions disabled, or otherwise, the chat does not load. It has worked temporarily a couple of times when I first turn on the computer, but as soon as I close the tab, or reload the tab, it stops working. In the past, I've been able to solve this by clearing the cache and cookies, and re-signing in, but that no longer solves it. Even that was inconsistent.

I have no idea how their chat is coded. Some of you might know what you're looking at when you inspect it. Ghostery is obviously blocking something. It's not maybe, it's not my imagination, other people are experiencing the same thing. My guess is there will be someone who can inspect that chat code and figure out what is holding it up.

Otherwise, my experience with Ghostery browser and search has been really very good and satisfying. I hope my report can continue to improve the project. Thanks.

seia-soto commented 3 weeks ago

Hi @OGHersch ,

I apologies for the inconvenience. However, the problem didn't show up for me, so it'd be great if you can confirm the reproduction step and the environmental information. From my view, the "chat" functionality in the website is the streamed chat in the random live video. The reproduction step for me is like the following:

  1. Sign in to website
  2. Click any live streamed videos
  3. Check if live streamed chat loads properly

on the following environment:

You can check the Ghostery Browser Extension version by clicking the Ghostery icon left to the address bar, then click menu button at top right, go to privacy protection. If you're still experiencing the issue, you may check the network panel in the devtools (open it by F12, Ctrl+Shift+I) then search for "stream". If you see the request blocked with a reason of "Blocked by Ghostery ...", I think we can make an improvement on this problem.

Best

OGHersch commented 2 weeks ago

Hey look at that. It seems like we are getting close to a resolve.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://web7.rumble.com/chat/api/chat/310084139/stream. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.

Ghostery Private Browser can’t establish a connection to the server at https://web7.rumble.com/chat/api/chat/310084139/stream.

Sent with Proton Mail secure email.

On Sunday, July 14th, 2024 at 2:02 PM, HoJeong Go @.***> wrote:

Hi @.***(https://github.com/OGHersch) ,

I apologies for the inconvenience. However, the problem didn't show up for me, so it'd be great if you can confirm the reproduction step and the environmental information. From my view, the "chat" functionality in the website is the streamed chat in the random live video. The reproduction step for me is like the following:

  • Sign in to website
  • Click any live streamed videos
  • Check if live streamed chat loads properly

on the following environment:

  • Ghostery Private Browser 2024.05.1 (86f09cb) (64-bit) on macOS 14.5 (23F79)
  • Ghostery Browser Extension v10.3.3
  • Germany geoIP

You can check the Ghostery Browser Extension version by clicking the Ghostery icon left to the address bar, then click menu button at top right, go to privacy protection. If you're still experiencing the issue, you may check the network panel in the devtools (open it by F12, Ctrl+Shift+I) then search for "stream". If you see the request blocked with a reason of "Blocked by Ghostery ...", I think we can make an improvement on this problem.

Best

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

seia-soto commented 2 weeks ago

Hi @OGHersch ,

The CORS error is not fixable at the frontend-level. The server can reject sending CORS proper headers by looking at the client activities so I may look at the network flow before that request. However, I cannot reproduce this problem from my end at the meantime.

One potential reasoning may be our browser is flagged as a bot from their server by looking at your symptom: clearing cookie helps. I'm really sorry but I cannot help without reproducing the issue. I'll try to reproduce the issue regularly but no luck right now.

OGHersch commented 2 weeks ago

that's cool. at least we're getting closer

Sent with Proton Mail secure email.

On Monday, July 15th, 2024 at 9:56 PM, HoJeong Go @.***> wrote:

Hi @.***(https://github.com/OGHersch) ,

The CORS error is not fixable at the frontend-level. The server can reject sending CORS proper headers by looking at the client activities so I may look at the network flow before that request. However, I cannot reproduce this problem from my end at the meantime.

One potential reasoning may be our browser is flagged as a bot from their server by looking at your symptom: clearing cookie helps. I'm really sorry but I cannot help without reproducing the issue. I'll try to reproduce the issue regularly but no luck right now.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

philipp-classen commented 2 weeks ago

I could reproduce the problem. It can happen that the live chat does not have any messages. Requests like https://web7.rumble.com/chat/api/chat/310084139/stream could indeed the problem, but I do not understand what is going on exactly.

The difference between a profile where it works and it does not work, seems to be that on the failing one, the requests fails with 502 Bad Gateway; when I open the URL directly, it also fails with 502 (even though the body inconsistently says 500 Service Unavailable). That also happens when I disable Ghostery (tested in the Ghostery Browser).

I also see the failing request being marked as a CORS error, but since it fails to load even in a new tab, this might be misleading. Opening the https://web7.rumble.com/chat/api/chat/310084139/stream URL in a separate tab should not result in CORS problems. That it still fails with 500 and even with the extension disabled, is weird.

error

OGHersch commented 2 weeks ago

Here is what I tried. I disabled the ghostery extension. Then I closed the browser completely and restarted it with the extension closed. The chat shows. Then, I can restart the extension and it continues to show without restarting the browser. I have to do that process each time I go to a different Rumble channel. Maybe that is a clue. We shall see. Thanks.

Sent with Proton Mail secure email.

On Tuesday, July 16th, 2024 at 2:35 AM, Philipp Claßen @.***> wrote:

I could reproduce the problem. It can happen that the live chat does not have any messages. Requests like https://web7.rumble.com/chat/api/chat/310084139/stream could indeed the problem, but I do not understand what is going on exactly.

The difference between a profile where it works and it does not work, seems to be that on the failing one, the requests fails with 502 Bad Gateway; when I open the URL directly, it fails with 500 Service Unavailable. That also happens when I disable Ghostery (tested in the Ghostery Browser).

I also see the failing request being marked as a CORS error, but since it fails to load even in a new tab, this might be misleading. Opening the https://web7.rumble.com/chat/api/chat/310084139/stream URL in a separate tab should not result in CORS problems. That it still fails with 500 and even with the extension disabled, is weird.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>