These kinds of installation issues are quite rare.

I'm not sure we have enough information to precisely tell you the problem or how to fix it, but maybe we can start to work it out.

FreeBSD (and thus pfSense) can boot using UEFI since FreeBSD 10.1, however, depending on the BIOS/UEFI in your laptop it might help to enable CSM (Compatibility Support Module) to allow booting in legacy BIOS mode. CSM enabled should generally be the most safe option (my experience).

Regarding AHCI or IDE this is mostly to do with your SATA ports, but may affect USB drives aswell. AHCI mode should be default, IDE being legacy mode for very many years now.

Installation to USB drives is generally a bad idea, since the controllers and NAND chips on USB drives are not really geared for that kind of workload. You should REALLY consider installation to a small SSD or even a Harddrive. At least to work out if the issue is related to the one or more USB drives, that you have attempted to use.

@NollipfSense @tompark
ok so here are the results of my efforts last night until 0130!
I am currently unable to get my plex to work.
the plex server is on the server 192.168.1.251 and I am trying to access it via the tv firestick. can anyone help?

Skynet.jpg

@araujovitorpaulo said in Help trying to get a new repo on my 2.4.4 p1:

@NollipfSense that was an alternative at the beginning, but when I search for updates, it says that the server is up to date (http://prntscr.com/rrnrc0).

The only way to recover it is making a brand new server with the 2.4.4p3 installation?

2.4.5 is the new current version. Unless you have an existing copy of the 2.4.4_p3 install media, it is no longer available from official sources. You may find unofficial copies out there someplace on the web, but I would be wary of such things.

You can do a frresh install using 2.4.5 media and import your existing configuration. There are instructions for doing that in the Netgate docs.

@onlyfor1question said in pfSense installation hangs at a certain screen:

@NollipfSense I just tried using that and I got the same error.

Sounds as if you're having hardware issue...try pfSense 2.4.5rc to see whether you have the same exact issue.

Olha, olhando o problema superficialmente, com as informações que você passou, já levando em consideração que você verificou cabos e etc, digo que sim o problema pode ser na placa de rede.

Não é normal ter problema de conectividade entre o pfsense e o modem, é um cabo, não é pra perder ping nem muito menos perder o MAC da tabela.

@ccigas said in Basic Firewall Set Up:

I guess from there, I would not have to allow DNS or HTTP/S through the firewall from there or is that not needed?

Typically, on an second LAN interface - called OPTx - you would block http and https acces to the Firewall (= pfSense) itself.
Don't block DNS, devices could use pfSense as a DNS, or whatever other DNS they want to use on the net.

@ccigas said in Basic Firewall Set Up:

For the DNS, it seemed to only work
pfSense doesn't use or care about DNS in receives from upstream routers.
The resolver - unbound - uses the 13 main root DNS servers (the real back bone of the Internet) to find domain info. That will always works.
There is no need - isn't used by default :
Ustream DNS servers,
ISP DNS servers,
Private info collection servers (Google and others);
etc.

If the default resolver doesn't work, something is wrong with your Internet access.

Btw : 'named' or bind, isn't used by pfSense. bind is much bigger and capable, and offers functionalities that hugely surpasses the needs of a firewall.