pretty URL not working
I have created a Virtual host and added this into the HOSTS file as well. Reboot the PC and when I enter the host name in the address bar, the page cannot be displayed: Reason: UNKNOWN , Notification: DNS_FAIL.
When i ping the site i do get a reply, howeveer when I do a nslookup, the proxy server cannot find. This is a local site (localhost). Why does the proxy block this and how can I fix this?
@Johanndut : Can you provide me some images? Do you know that Laragon automates the processes for you so you don't need to manually add them.
Yes I have re-created it useng the automated process, and even this gave me the error. However when i put in http://localhost:8080/hta.site1/public/ I do get the laravel index page displayed.
Can you also show me your hosts file and the virtual host file?
I managed to get this working. Port 80 was taken by the system PID=4. But I have setup the apache server to use port 8080. This caused the problesm.
Thanks it is working now
I'm glad to hear you sorted it out Cheers!
@leokhoa i meet the same problem.
i cannot open my web too.
@Yuki-Ryu : Don't use
@leokhoa i have use another TLD still same.
and what make me more confused almost everytime want to reply like this,
I got mine to work eventually. The problem is with the port. Even though you have the option to change the port, the port should be 80. I don't know why you have the option to change the port if it does not work with another port.
Just have a look what other service is using Port 80. suspend the service and repoad the laragon. The prettyURL will work then
I'm glad to hear you found the issue
If you change the port, just append it to the url:
Hi. Yes I tried that and still got the problem... Tried port 8080 and no luck. Port 80 (default) that was working.
@Johanndut i have tried change the port to 8080 and still error even the error change from(secure connection failed, error code: ssl_error_rx_record_too_long)
to(400 bad request, Your browser sent a request that this server could not understand.
Additionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle the request.)
is there any other ways to fix it?
@Yuki-Ryu Well, I could not find any solution. Eventually I had so use port 80 and the service on my PC that used port 80 had to use another port.