How to create login credentials for info and status page?

[Richard G]

Nowadays a file called /etc/httpd/conf/extra/httpd-info.conf.secret is present.
This contains some pre-generated username and password which is commented out.

Uncommenting and using that name (info) and password is not working.
I tried creating a password and username the same as I do for .htpasswd files, but that does not work either.

Tried plaintext password, but no matter what, I get a 401, page just reloads.

So how can I create a working username and password in there?

 

[zEitEr]

The file contains only plain text credentials for an admin. If you change the file it won't effect anything at all. Use credentials from the file to access https://server.domain.com/server-status

 

[Richard G]

Oh that's not great. Because on all servers it's username info and some long password.
Not a great idea if the content can't be changed to something else. It also gets re-created when doing the rewrite_confs command.

In that case it seems best to me to keep using the old method with the httpd-info.conf in the custom directory.
Unless the /var/www/passwd-server-status file is not overwritten and we can keep an md5 username and password in there. That works too.

 

[zEitEr]

More reading: https://docs.directadmin.com/webservices/apache/general.html#how-to-check-apache-server-status

If you don't like how it works, you're welcome to post a request describing how you think it should work. Probably Directadmin developers will accept it.

 

[Richard G]

More reading:

I've read that, but that's exactly what I stated that it's always username info and some long password. No further explanation.

So in fact:
a.) it's always username info and some password
b.) there is no explanation at all about if it can be changed or editted or not
c.) Added to confustion is that the lines are commented, giving the impression that this is an example or that one has to remove the comments for it to work because it's a kind of hardcode plaintext password
d.) Explain that it will be re-created by using the da build rewrite_confs command.

That were some docs improvements.

You're welcome to post a request describing how you think it should work.

That I also just kind of did. Make it edittable so one can put in a custom username and password or change the current one like one would expect.

Or add that one can instead use a custom username and md5 password in the /var/www/passwd-server-status file (unless that can get overwritten by an update or something)