by Golgi » 31 May 2019, 10:37
by englishtim » 31 May 2019, 11:31
by dragos_nedelcu » 31 May 2019, 15:31
by Ears of Tin » 31 May 2019, 20:12
by Colin » 31 May 2019, 20:21
by Tantal » 01 Jun 2019, 10:51
by tml3nr » 01 Jun 2019, 10:57
RandomRuneUser wrote:dynobot wrote:Would something like iftop or some other network monitoring tool be of use to determine what is trying to connect to what and holding up the UI?
using iftop I can see lastfm-api-vip1.phx1.cbsig.net as possibly being the problem....any way to remove this from Rune?
I ran a trace on my router and saw timeouts with my pi connecting to api.dirble.com that corresponded closely to the delays in the UI. Just blocking that IP did not work, but wildcard-blacklisting dirble.com on my pi-hole did.
If you don't have control over your DNS, probably you could edit the hosts file on your rune box (or whatever the equivalent is ... I'm not super familiar with arch linux.)
Edit: can confirm that adding the following to /etc/hosts works:
127.0.0.1 api.dirble.com dirble.com
by Toube » 02 Jun 2019, 16:14
by anana » 05 Jun 2019, 08:41