Cant checkout into BETA

[lenu]

Hi,

clean RASPBIAN and Pihole installed today.
Its the new Raspberry PI3 B+

when it comes to:
pihole checkout core FTLDNS

it takes long, after finished

i ran: pihole checkout web FTLDNS
and it feezes at starting Point "[i] Fetching branches from https://github.com/pi-hole/AdminLTE.git"
nothing, half an hour.
I repaired, rebooted, switched other DNS in Network off and so on.
Nothing. Cant get BETA work

Debug TOKEN: rsedoaojsc

[lenu]

..... i am now .... somethere else.

  [✗] Backing up index.lighttpd.html
      No default index.lighttpd.html file found... not backing up

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script

  [i] FTL Checks...
  [✓] Detected ARM-hf architecture (armv7+)
  [i] Checking for existing FTL binary...
  [✗] Downloading and Installing FTL
  Error: Unable to get latest release location from GitHub
  [✗] FTL Engine not installed
  [i] Restarting services...
  [✓] Starting lighttpd service
  [✓] Enabling lighttpd service to start on reboot
  [✓] Starting pihole-FTL service
  [✓] Enabling pihole-FTL service to start on reboot
  [✓] Deleting existing list cache
  [✗] DNS resolution is currently unavailable

It showed me, theres an Update available for FTL ......
but i can't update with pihole -up.....

somehow while switching to BETA it lost all capability to connect to Internet.
I did everyhing and now I inserted NS from Cloudflare into resover.conf ....
This is a temp fix? what can i do?

[DanSchaper]

@lenu

rsedoaojsc

What does dig github.map.fastly.net from the Pi-hole terminal show?

[lenu]

it showed some requests.
sorry for bothering, i tried all day, i made everything like last time with dev.
I noticed that the Version today "adminLTE" from dev is something else.
It seems that code somhow has changed and this wont work for me.

I am glad to have some PI running with:

pihole -v

Pi-hole version is v3.3-181-ga7e7680 (Latest: v3.3.1)
AdminLTE version is v3.2.1-195-g4355bde2 (Latest: v3.3)
FTL version is vDev-5ecab0a (Latest: v3.0)

But everything i tried today, same procedure with Unbound and DEV checkout DIDN't worked at all.
Nothing. I tried 6 Hours....

I will not run my second PI with DEV as its to buggy for me Sorry.

[mibere]

There were several users with GitHub issues in the past days Strange.

[DanSchaper]

Somewhere fastly.net got added to a blocklist I think, there are problems with that domain being accessed.

[lenu]

You can belive me or Not - i really thought the same. Somehow request to git etc. Never finished. Sometimes it felt like only having installed half of the scripts. There Where basicly things which didnt worked. My goal was to record a Tutorial for Friends. Instead of my half Hour it webt up to whole day ..... really annyoing!

I also had Problems updating new Blocklist. (Freezing)

[lenu]

Today, again:

i ran:

pihole checkout core FTLDNS

took a while, but went through.

i ran:

pi@raspberrypi:~ $ pihole checkout web FTLDNS
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y

[i] Fetching branches from GitHub - pi-hole/web: Pi-hole Dashboard for stats and more

And thats it.
I wont come to an end. Maybe some redirect Issue/ wrong URL? "GitHub - pi-hole/web: Pi-hole Dashboard for stats and more"

EDIT:
OH WOW.
After 23 min, i got output:

  [i] 16 branches available for Web Admin

  [✓] Switching to branch: 'FTLDNS' from 'refs/heads/master'
  [i] Already up-to-date.

Now it worked. At least Backend changed, i didn't test the rest.

[mibere]

I recommended it already, maybe you should whitelist needed domains by default - or even hard-code it in an internal, not changeable, whitelist.

[DanSchaper]

We've had the discussion and we don't think it's a good idea for us to start whitelisting domains, we are removing the default whitelists that we use now as it can be easily construed that by default whitelisting we are similar to another package that is inserting domains that they find acceptable and allowing adverts through. I know that it would only be domains that we serve our content through, but on the whole a default whitelist is not the best approach.

[mibere]

Bandwidth shortage at Github? Because the "whole world" is migrating data away from GitHub?

[mibere]

An user in the Telegram group had the same or similar download difficulties. It worked for him after changing the system locale to EN. He followed the steps in post 21 of Fetching branches fails - #21 by Samioul.

[bostonvex]

Must be the Microsoft acquisition that broke it