Amahi Forums

Made the Listen 8081 change on one test server and things seems to work fine. I could get to wolserver in the network and add machines and users. It's been a day or two and now all of my apps do not resolve correctly. I ran Amahi's Interactive Network Troubleshooter and came up with the error: "** server can't find hda: NXDOMAIN" The only other change I can think of that I made to that server is this morning I installed Webmin from the .rpm on the Webmin site.

How do I troubleshoot "** server can't find hda: NXDOMAIN?"

I have discovered a minor change to the procedure for running apps on a different port. Rather than modify /etc/httpd/conf/httpd.conf, you can do the following for the app:

Listen 8081
<VirtualHost *:8081>

Adding the line as the first line in the ###-appname.conf file works the same as adding it to httpd.conf. This is a cleaner way to do it and will ensure if you don't want an app on a port, httpd is not listening on the port. Always best to not modify httpd.conf file as it could break the web server.

Does that make sense?

As for you current problem, recommend you check the client DNS to ensure it's using the HDA. For a Windows machine, just do:

Actually, I cannot get the apps to resolve even on the server, The warning that I posted is on the Amahi server. Something is off with the DNS of the server. How do I troubleshoot this?

OK, I changed the /etc/httpd/conf/httpd.conf and dropped the Listen 8081 and things are back as they should be. I will try the other method that you have mentioned. Lets see.

It works. I did test it

I still have not added the wiki guidance yet. It's on my list.

As for you other issue, verify the DNS server is enabled and running on the HDA. It's in the Dashboard under Network, Settings.

Nice icon and screen capture added to the App. Where did you get the icon? I like it.

I updated the WOL wiki. Feel free to adjust it as needed.

Google

Once you finish your testing, we should be able to release this one LIVE.

Thanks for making the updates and I will check out the wiki guidance.

Made updates to the wiki guidance. I also have put the new instructions for exposing web apps to the internet at Hosting Webapps (Alternative).

This gives users a choice and keeps duplication of guidance to a minimum.

I have tested the VirtualHost method of changing httpd.conf and had problems on both servers. The method of changing the .conf file for the app seems stable. I want to run it for a few more days and see what happens. Good work.

I was afraid that might happen. Not a big fan of editing httpd.conf so that's why I came up with the other method. It should prove solid.

Good work by all.

I would like to see the web UI spruced up a bit though. I think adding buttons vs links for the menus would be nicer. Did you check out the sceen shots from the AMS app that I uploaded earlier a while back?

Adding buttons is not too hard in php