lets try again.

What the fuck is with apache. Why I cannot start the page. it should be 5 minutes work.

but it give some shitty error where it is not clear what is wrong

This site can’t be reached timetracker.local’s server IP address could not be found.
Try:

Checking the connection
Checking the proxy, firewall, and DNS configuration
Running Windows Network Diagnostics
ERR_NAME_NOT_RESOLVED

how long apache is being developed? 10 years ? more? and cannot make normal error messages so you would know how to fix the problem . fuck that. I hate it so much. wasting my time. bastards.

please somebody help me to fight this shit

Are you sure this is problem of Apache?

"IP address could not be found" is usually a client side error. What does Apache's log say?

@sbiewald

https://pastebin.com/nWA9XgN0

@sbiewald I am not sure but usually it is. Where else can be the problem? By client side what do you mean? javascript? I doubt it. I could add die() to index php and it still would not load

@Angry-dev No, this kind of error is usually shown by the web browser, when the Server is not reachable or the DNS entry points to a wrong site.

Of course webapps can show this, too, when they can't reach some back end endpoints, but this is hardly the server's fault.

To the logs: Is Apache crashing after 7 seconds? Are there any more logs or can you increase the verbosity of the logs?

To check: Do you run apache on your computer itself? Is the server than reachable on 127.0.0.1? This will exclude hostname / DNS problems.

@sbiewald "when the Server is not reachable or the DNS entry points to a wrong site."

Yes, but why server is not reachable? Is it not because of apache config?
How do I know if DNS points to a wrong site?

"To the logs: Is Apache crashing after 7 seconds?"
Apache is not crashing, it is still runing.

There are access logs but I guess they do not how much useful info

https://pastebin.com/XRfcJCFZ

I have increased level log to debug, and then tried runing site, I also tried localhost:8081 which runs index.php in the root, and
localhost:8081 works , port number I have added somewhere in config instead of 80.

https://pastebin.com/NNhpCYmL

I run the site locally on my computer.

Try adding the DNS name to your hosts file. Seems like your computer doesn't know it.

@Angry-dev

To check DNS resolving you might try on the commandline 'ping <hostname>' where '<hostname>' is the name you want to check. While ping is usually for checking if a host is available in a network, the tool also resolves DNS.

@PrivateGER I have added

timetracker.local 127.0.0.1

@sbiewald

ping timetracker.local
Ping request could not find host timetracker.local. Please check the name and try again.

I am not sure how can it not find it if I have added it to hosts file.

Ok, I tried to seach of hosts file examples and turned out that first I should have written IP, then domain name. And then ping returns reply.

What the fuck windows creators think by not adding a validation? This error is easily done by humans. This is just stupid. Or they should make a UI which would update that file and so we would never make that mistake.

Ok but still site does not load. Chrome shows

This site can’t be reached timetracker.local refused to connect.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED

Apache does not add new logs after I changed hosts and refreshed page.

Actually later remembered that port 8081 and tried to set it in virtual host instead of 80, then go to timetracker.local:8081 and finally it works.

So the main problem this time was windows , not the apache. But probably linux also would not tell about wrong hosts file, would they?

Thank you guys for the relativelly quick support.
How should I have know this. I though on this site people are only ranting but this is cool that you can get even help. I hate like on stack overflow if you rant, you get downvotes and they can even suspend your account when you have lot of downvotes. But those problems really make feel like shit and almost without power to do anything when you do not have guru sitting near you.

@Angry-dev No operating system will complain outside of logs (I don't know if Linux or Windows do log that).

I dont think Apache is the problem