I ended up "fixing" the issue by rebooting the server. Still trying to
track down the initial cause.
On 9/3/15 4:15 AM, Pascal Quantin wrote:
>
> 2015-09-03 13:04 GMT+02:00 Robert Cragie <robert.cragie@xxxxxxxxxxxxx
> <mailto:robert.cragie@xxxxxxxxxxxxx>>:
>
> I can't access https://code.wireshark.org/review - is it down?
>
>
> Hi Robert,
>
> I also get a 502 proxy error. We'll need to wait for Gerald's maintenance I
> guess.
>
> Pascal.
>
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>
