Unable to connect using a browser

---

jjcf89_2 wrote:

Beware the tls addon is currently breaking systems.  Check the issues section before going ahead with the install

---

To clarify - it appears to be failing on systems that have atom cpus.  Unfortunately, that includes Ultra - but not Ultra Plus or Pro.

WhoCares_:  is this something you are looking at fixing? 

IMO converting to OS-6 is a better option, and the affected systems should be able to be converted.

---

StephenB wrote:

---

---

To clarify - it appears to be failing on systems that have atom cpus.  Unfortunately, that includes Ultra - but not Ultra Plus or Pro.

 

---

Not true.  The Ultra4Plus/Pro4 has an Atom D510 @ 1.66GHz and an Ultra2Plus/Pro2's has an Atom D525 @ 1.80GHz.  The Ultra4 has a D410 @ 1.66GHz, and I've never had an Ultra2, so can't quickly check.

My 4.2.31 sandbox system is a Pro2, and the add-on fails.  I've tried several times from a factory default and have had results where it just does nothing and others where the GUI is completely inaccessible, even with a browser that previously worked.

---

Sandshark wrote:

---

StephenB wrote:

---

---

To clarify - it appears to be failing on systems that have atom cpus.  Unfortunately, that includes Ultra - but not Ultra Plus or Pro.

 

---

Not true.  The Ultra4Plus/Pro4 has an Atom D510 @ 1.66GHz and an Ultra2Plus/Pro2's has an Atom D525 @ 1.80GHz.  The Ultra4 has a D410 @ 1.66GHz, and I've never had an Ultra2, so can't quickly check.

 

---

GTW - I didn't realize the 2-bay and 4-bay Pros and Ultra Pluses also used atom processors. My only Pro is the Pro-6. 

Folks can easily identify the processor with ssh - this command will do the job:

cat /proc/cpuinfo

In any event, all these systems can be converted to OS-6, which I think we both agree is a better solution.

---

jjcf89_2 wrote:

---

If I can unbrick my unit, I might just go with the remove the http redirect approach

 

---

An OS reinstall should restore the broken library (and change your admin password back to netgear1).

I couldn't test the change to virtual.conf for 4.2.x systems (as I no longer am running 4.2.x). It's be useful to know if it also works with 4.2.x.  I suspect it will, but there might be some other changes needed in httpd.conf.

---

StephenB wrote:

---

jjcf89_2 wrote:

---

If I can unbrick my unit, I might just go with the remove the http redirect approach

 

---

An OS reinstall should restore the broken library (and change your admin password back to netgear1).

 

I couldn't test the change to virtual.conf for 4.2.x systems (as I no longer am running 4.2.x). It's be useful to know if it also works with 4.2.x.  I suspect it will, but there might be some other changes needed in httpd.conf.

---

Okay that sounds promising, I wasn't sure how much of the files would be restored by the OS reinstall.

I'm familiar with apache configs, I can take a look assuming I get back to it.

To update:

> An OS reinstall should restore the broken library (and change your admin password back to netgear1).

The os reinstall did not work.  The system hung on the "Booting ..." screen like before.

However now when I try to chroot in tech support mode, I get a malloc error.

# chroot /sysroot

malloc: unknown:0: assertion botched
free: called with already freed block argument
last command: (null)
Aborting...Aborted

Ouch.  Not something I expected, with only the one library being updated in the add-on.

Can you run commands directly from sysroot?  For example, 

# /sysroot/bin/df . -h

Rusty posted fixed deb files.  Which got my system back up and running. https://github.com/rdynsxtrs/rn4bin/issues/3

I installed the new package on a freshly factory defaulted Pro2 running 4.2.31.  Though, after an inordinately long period of time, it ultimately reported an error in the installation, it works.