Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#27392 closed defect (fixed)

Moat url update

Reported by: hiro Owned by: brade
Priority: Very High Milestone:
Component: Applications/Tor Launcher Version:
Severity: Normal Keywords:
Cc: gk, mcs Actual Points:
Parent ID: Points:
Reviewer: Sponsor:



I have deployed moat on an Azure VM.

Here are the details:

The moat distributor is working, but I have issues retrieving bridges. I will update this ticket as soon as I have more news.

Child Tickets

Change History (6)

comment:1 Changed 2 years ago by brade

Cc: gk mcs added

comment:2 Changed 2 years ago by gk

Priority: MediumVery High

comment:3 Changed 2 years ago by hiro

Hi, you should now be able to receive a bridge if you test the urls in torbrowser.
Please let me know if you have any issues.

comment:4 Changed 2 years ago by gk

Resolution: fixed
Status: newclosed

I get a bridge, thanks! So, I wrote a patch with the URL update and committed it to master (commit 7779e8a8dbfa81c01a2fbc3be596f851e54176ad).

Two things, though:

1) One gets only one bridge while in 8.0a10 one gets three. Could you please change that behavior? In case a user gets just one bridge and that is currently broken that's not so cool. :)
2) One gets the same CAPTCHA everytime while in 8.0a10 one gets a new one with every request. I think we should keep that behavior.

comment:5 Changed 2 years ago by hiro

I am trying to understand why I always get one bridge. I believe this is because I see an error in my logs about not enough bridges of the type specified to fulfill the request.

I have been talking to Matt to see if is it something in my configs.

Meanwhile I have generated more captchas so that one gets a new one with every request.

comment:6 Changed 2 years ago by hiro

Please update the urls as follow:
extensions.torlauncher.moat_service ​
extensions.torlauncher.bridgedb_reflector ​

Note: See TracTickets for help on using tickets.