Everytime i switch to dev version and restart i get an error!

Started by opnsenseuser, August 15, 2018, 01:32:44 PM

Previous topic - Next topic
installing the prod i had no problem. 18.7.1

but by switching to dev (19.1) and reboot i get the error:

Enter full pathname of shell or RETURN for /bin/sh: ENTER

so i installed opnsense several times and i get the error everytime.

what can i do? see my screenshot for more details.

thx
rené
Supermicro A2SDi-4C-HLN4F
Team Rebellion Member (sidebar / themes: tukan, cicada & vicuna)


thx franco  :)

So a common problem. I thought it was only up to me!
Supermicro A2SDi-4C-HLN4F
Team Rebellion Member (sidebar / themes: tukan, cicada & vicuna)

Fixed on git master, packages follow in the next hour. Sorry for the trouble.


Cheers,
Franco

No Problem Franco.

Thx :-)
Supermicro A2SDi-4C-HLN4F
Team Rebellion Member (sidebar / themes: tukan, cicada & vicuna)


everything works great now!

thx franco!!  ;D
Supermicro A2SDi-4C-HLN4F
Team Rebellion Member (sidebar / themes: tukan, cicada & vicuna)

Today i could not make a connection to the plugins using firmware update. no plugins -> folder is empty acccept those plugins which i installed yesterday.

opnsense-code core
cd /usr/core
make upgrade
make upgrade CORE_RADVD= CORE_SQUID=


nothing of these commands work!

Am i missing something or doing wrong?
Supermicro A2SDi-4C-HLN4F
Team Rebellion Member (sidebar / themes: tukan, cicada & vicuna)

There was a new topic at https://forum.opnsense.org/index.php?topic=9451.0 but here is more debug info.

You have a SSL proxy in your network misconfigured.

The dev version switched to HTTPS for the package repositories and you can't connect to them anymore.

The core code can't be loaded because opnsense-code wants to install git from the repository but that fails too.

That's also why you don't have a list of plugins anymore. Your connection to the mirror is severed. :)

You can fix this temporarily by going to System: Firewall: Settings and selecting a HTTP mirror (not HTTPS).

The proper fix would be to exclude pkg.opnsense.org from the SSL proxy...


Cheers,
Franco