Upgrading to webmin 1.480 caused BIND module to go missing. Since then, BIND module is missing from both the webmin list and the 3rd party modules list from within webmin.
Ok, that's the real issue .. that means that webmin cannot detect your OS properly. You should fix this at Webmin -> Webmin Configuration -> Operating System and Environment
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-10-13
Okay. But I don't understand why this stopped working all of a sudden, and why webmin can't automatically detect the system any more. I had version 1.470 working without these problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-10-13
So I installed the BIND8 module from webmin. When I click on it, it now says "Error - Missing Content-Type Header".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you sure it doesn't appear under the "Un-used Modules" category?
If so, does clicking "Refresh Modules" move it to the correct "servers" category..
I already tried that. It does not appear under unused modules, before or after a refresh.
What if you go to https://yourserver:10000/bind8/ in your browser directly?
It says "The BIND DNS Server module is not available on your system".
Which OS are you running Webmin on there?
OSX 10.5.8
That should work then .. what does the os_type= line in your /etc/webmin/config file contain?
os_type=
It is blank, as is real_os_type.
Ok, that's the real issue .. that means that webmin cannot detect your OS properly. You should fix this at Webmin -> Webmin Configuration -> Operating System and Environment
Okay. But I don't understand why this stopped working all of a sudden, and why webmin can't automatically detect the system any more. I had version 1.470 working without these problems.
So I installed the BIND8 module from webmin. When I click on it, it now says "Error - Missing Content-Type Header".
I'm not sure how that could happen either.
If you don't have any complete custom configuration changes made to Webmin itself, it may be simpler to just un-install and re-install.