Amahi Forums

If you're getting a big error when trying to load your Amahi dashboard, try this to fix it:

If you're on 64-bit: Otherwise: We're working on a better fix... one that won't require user intervention...

UPDATE: the links above have been updated - please try them and report below!

I have a install on Fedora 12 (64bit). It's running in a KVM VM as a trial. I don't have the spare hardware to play with at the moment. Anyway, I had the whole fundamental error thing on the dashboard after the install. It, never worked.

Tried this fix and now have this error:

Same thing for me. Funny thing is, system is working, although I cannot access it via http://hda. It actually started handing out IP addresses and I could see the shares thru my MVIX Ultio Pro box. I am not sure if I should just try re-installing, or hold out to see if there is a potential fix.

These have been released to the f12 repo, so updates from the HDA's automatics updates should pick them up automatically!

Please do report if there are still any issues!

MANY THANKS to the many that helped triage, test and debug this very nasty issue. We took the opportunity to learn and correct the packages involved to make them easier down the line!

Greetings:

I updated with the update manager and still same issue. Maybe my local repo still hasn't updated. But I can assure you that the code/link provided worked like a charm.

Thank you very much. Greatly appreciate those involved

Fix seems to have worked, allowing me to access dashboard via http://hda. I still get an 'unable to connect' when trying to access http://localhost:2000. Thanks for your hard work, and let em know if you have any suggestions for the amahi-installer issue (or if I even need to be concerned about that)

Fix seems to have worked, allowing me to access dashboard via http://hda. I still get an 'unable to connect' when trying to access http://localhost:2000. Thanks for your hard work, and let em know if you have any suggestions for the amahi-installer issue (or if I even need to be concerned about that)

If http://hda works, it means the installer was previously run.
Port 2000 is closed once the installer is done, so you won't be able to access it again that way.
Why do you want to access http://localhost:2000, if http://hda is working?

I guess that I don't. I couldn't remember (from a previous trial install) if there was configuration work that needed to be done at that address. Sort of new to all this, so just feeling my way around. Thanks again for the fix.

Great to hear things are working!

I suppose we could make it so that it gets picked up automatically, however, this will only get hit by people who update by hand, in which case, the fixed package will be picked up anyway.

Thanks for the feedback!