I’m sure this is already reported.
Getting this error on matray
“Error getting news” Bad Gateway
4 Likes
Hi @MAYBL8,
That’s possibly because your system wasn’t updated for some time, which you shouldn’t do in any case. In the matray Settings window, what is the Server URL value set to?
I’m on unstable.
Updating whenever I see there is an update needed.
https://manjaro.news
What happens if you browse to that URL?
And please post the output of:
ping -c 4 manjaro.news
and
traceroute manjaro.news
[demo@manjaro ~]$ ping -c 4 manjaro.news
PING manjaro.news (94.130.177.69) 56(84) bytes of data.
64 bytes from static.69.177.130.94.clients.your-server.de (94.130.177.69): icmp_seq=1 ttl=50 time=135 ms
64 bytes from static.69.177.130.94.clients.your-server.de (94.130.177.69): icmp_seq=2 ttl=50 time=135 ms
64 bytes from static.69.177.130.94.clients.your-server.de (94.130.177.69): icmp_seq=3 ttl=50 time=133 ms
64 bytes from static.69.177.130.94.clients.your-server.de (94.130.177.69): icmp_seq=4 ttl=50 time=134 ms
[demo@manjaro ~]$ traceroute manjaro.news
traceroute to manjaro.news (94.130.177.69), 30 hops max, 60 byte packets
1 _gateway (192.168.68.1) 5.761 ms 6.643 ms 6.637 ms
2 * * *
3 te0-14-0-8---0.lcr01.clwr.fl.frontiernet.net (172.99.44.192) 17.564 ms 17.561 ms 17.543 ms
4 * * ae8---0.scr02.mias.fl.frontiernet.net (74.40.3.73) 31.426 ms
5 ae0---0.cbr06.mias.fl.frontiernet.net (45.52.201.157) 25.004 ms ae1---0.cbr06.mias.fl.frontiernet.net (45.52.201.159) 22.748 ms ae0---0.cbr06.mias.fl.frontiernet.net (45.52.201.157) 22.740 ms
6 4.2.240.253 (4.2.240.253) 22.763 ms 19.228 ms 24.806 ms
7 * * *
8 195.122.181.130 (195.122.181.130) 129.953 ms 128.876 ms 195.122.182.238 (195.122.182.238) 128.901 ms
9 ae6-2011.nbg40.core-backbone.com (80.255.14.246) 138.493 ms 136.325 ms ae1-2014.nbg40.core-backbone.com (81.95.15.206) 133.759 ms
10 core-backbone.hetzner.com (81.95.15.6) 134.314 ms core-backbone.hetzner.com (5.56.20.254) 129.891 ms core-backbone.hetzner.com (81.95.15.6) 138.606 ms
11 213-239-245-73.clients.your-server.de (213.239.245.73) 137.753 ms core11.nbg1.hetzner.com (213.239.203.137) 138.800 ms 213-239-245-77.clients.your-server.de (213.239.245.77) 153.345 ms
12 spine12.cloud1.nbg1.hetzner.com (213.239.239.122) 136.874 ms 136.866 ms spine14.cloud1.nbg1.hetzner.com (213.133.112.82) 136.862 ms
13 spine1.cloud1.nbg1.hetzner.com (213.133.112.46) 129.411 ms spine1.cloud1.nbg1.hetzner.com (213.133.108.162) 140.723 ms 134.702 ms
14 * * *
15 12349.your-cloud.host (116.203.161.118) 137.954 ms 141.706 ms 140.314 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
I do believe the news server is down for some reason. because the server pings, but visiting https://manjaro.news/ returns
502 Bad Gateway
nginx/1.18.0
It’s server-side issue.
1 Like
Just got the same here, when testing. So I do believe it’s time to ping @philm, @moson or someone that I don’t know who that someone is…
Pinging @Weidenwiesel
7 Likes
Same here. Waiting…
Same issue here with my system.
The best support as it is 
So… is this being worked on?
Or should I just remove matray?
It’s not like this came out of nowhere, the original author/host notified well ahead of time.
That this still happened tells me that nobody feels responsible and when nobody feels responsible it’s generally best to just ditch a piece of software.
The matray depends on a voluntary service run by a forum member.
Your guess is as good as mine - It is likely the member is elsewhere occupied and matray has gotten low priority.
I have never used the service 
I’m getting this also, but at work only (my home machines don’t have this problem), and starting today only (8AM PST Tue Nov 22, 2022), even though the earliest reports in this thread are from 2 days ago. Odd that some computers get “Bad Gateway” and some don’t; I would have thought it was a purely server-side thing, but maybe not.
Addendum, Tuesday afternoon after work, at home: Turns out, the only reason my other machines don’t display the error every 10 minutes like my work machine does is, the error messages are disabled.
So it’s purely server-side. Whoever is minding the “news” site is apparently off on vacation (or busy with work, or in jail/hospital/morgue/military/etc). People have lives to live. So either it eventually gets fixed or I’ll just remove the icon from my system tray.
Besides, it’s not like we don’t know when Manjaro has an update for us: our Pamac tray icons turn red with tooltip reading “You have 539 updates!”. 
The same… Well, the only thing I would like to say in that case…
Just adding myself to this thread as well, I’m experiencing the same error and seeing the same 502 for the last few days.
It’s November here too!
Should it be part of a normal Manjaro installation, then, if the team cannot make sure that it actually works?
An “official” part of the installation that just flat out doesn’t work because one voluntary is currently not available is an extremely unprofessional look.
I might be wrong here, but I cannot remember installing matray myself, so I assume it came with the installation.
If I’m right, I’d suggest at least removing it from the installation package, if that hasn’t been done already.
2 Likes
It’s been removed.
1 Like
that’s a bummer. I did really like the way it made it easy to get across to the forum to catch detailed patch notes.
2 Likes