Not connecting to Localhost

Kilo · Mar 3, 2016

I'm using Windows 10, and IIS however for some reason Localhost doesn't seem to want to work? I'm aware it's a general issue with Windows 10 however, are there any solutions available?

Thanks.

Ecko · Mar 4, 2016

Check if something else is running on port 80

Marq · Mar 4, 2016

eckostylez said:
Check if something else is running on port 80

What he said, try that and make sure xampp and stuff is loading. If you have skype in the background close it, was one of the issues for me.

LeChris · Mar 5, 2016

Marq said:
What he said, try that and make sure xampp and stuff is loading. If you have skype in the background close it, was one of the issues for me.

He said he is using IIS. The easiest fix is just a quick restart, honestly and to check to make sure the server, and generic website is started.

Marq · Mar 5, 2016

Leader said:
He said he is using IIS. The easiest fix is just a quick restart, honestly and to check to make sure the server, and generic website is started.

Yeah, or try that.

eh

TheCanadian · Mar 5, 2016

noobs tryna help other nobbs, I'm sorry lmao.

on topic; what exactly do you mean it's not working? can you upload the logs file with the specific errors?

LeChris · Mar 6, 2016

TheCanadian said:
noobs tryna help other nobbs, I'm sorry lmao.

on topic; what exactly do you mean it's not working? can you upload the logs file with the specific errors?

Hopefully, I wasn't included within that list of noobs. If he restarted his computer, IIS would be a start up priority, versus other programs using port 80 thus making it work. Also, sometimes the server will not even start the website automatically, in which he'd need to do it himself.

Also, stick to one form of spelling "noobs" to "nobbs" is not the best transition.

TheCanadian · Mar 7, 2016

Leader said:
Hopefully, I wasn't included within that list of noobs. If he restarted his computer, IIS would be a start up priority, versus other programs using port 80 thus making it work. Also, sometimes the server will not even start the website automatically, in which he'd need to do it himself.

Also, stick to one form of spelling "noobs" to "nobbs" is not the best transition.

it's not that deep bruh, you can't really know what's going on without viewing the specific errors; the log file will give you a better understanding

Ecko · Mar 7, 2016

TheCanadian said:
it's not that deep bruh, you can't really know what's going on without viewing the specific errors; the log file will give you a better understanding

shut up noob

TheCanadian · Mar 7, 2016

eckostylez said:
shut up noob

you seem like a troll, get back on topic

Ecko · Mar 7, 2016

TheCanadian said:
you seem like a troll, get back on topic

dunno why there are any other posts in this topic, since my initial reply was the proper way of debugging this

TesoMayn · Mar 7, 2016

eckostylez said:
dunno why there are any other posts in this topic, since my initial reply was the proper way of debugging this

Because people are stupid, and no one knows how to check logs to see the errors. They'd rather be lazy idiots their entire lives and have people solve their problems.

Ecko · Mar 7, 2016

DonaldTrump said:
Because people are stupid, and no one knows how to check logs to see the errors. They'd rather be lazy idiots their entire lives and have people solve their problems.

Another reason why IIS sucks (contrary to what @Jaden believes). Apache/Nginx/Litespeed - would take me 5 seconds to tail the logs whereas IIS wants you to open up Event Viewer just to find that out.

Jaden · Mar 7, 2016

eckostylez said:
Another reason why IIS sucks (contrary to what @Jaden believes). Apache/Nginx/Litespeed - would take me 5 seconds to tail the logs whereas IIS wants you to open up Event Viewer just to find that out.

You can view a raw log file with IIS.

Ecko · Mar 7, 2016

Jaden said:
You can view a raw log file with IIS.

No shit, really?? Damn that makes IIS the best!!

Jaden · Mar 7, 2016

eckostylez said:
No shit, really?? Damn that makes IIS the best!!

I know right !!!!!

LeChris · Mar 7, 2016

eckostylez said:
Another reason why IIS sucks (contrary to what @Jaden believes). Apache/Nginx/Litespeed - would take me 5 seconds to tail the logs whereas IIS wants you to open up Event Viewer just to find that out.

Litespeed is my bae rn

TesoMayn · Mar 7, 2016

All of you plebs barely know how to use Apache, so you should stick to that.

As for the topic of this thread, post the logs if you can't understand them yourself.

griimnak · Mar 9, 2016

Kilo said:
I'm using Windows 10, and IIS however for some reason Localhost doesn't seem to want to work? I'm aware it's a general issue with Windows 10 however, are there any solutions available?

Thanks.

something may be using IIS's port, this was my problem.

Code:

netstat -aon

use this to check if anything is using that port (80)

Code:

NET stop HTTP

use that to kill the interfering services

Ecko · Mar 10, 2016

griimnak said:
something may be using IIS's port, this was my problem.

Code:

netstat -aon

use this to check if anything is using that port (80)

Code:

NET stop HTTP

use that to kill the interfering services

bad

use netstat -anb and you can see the actual processes/services

Not connecting to Localhost

The King.

23:37 [autobots] -!- eckostylez [[email protected]]

New Member

John 15:18

New Member

Jordan behind you ;P

John 15:18

Jordan behind you ;P

23:37 [autobots] -!- eckostylez [[email protected]]

Jordan behind you ;P

23:37 [autobots] -!- eckostylez [[email protected]]

Boredom, it vexes me.

23:37 [autobots] -!- eckostylez [[email protected]]

not so active

23:37 [autobots] -!- eckostylez [[email protected]]

not so active

John 15:18

Boredom, it vexes me.

You're a slave to the money then you die

23:37 [autobots] -!- eckostylez [[email protected]]

Users who are viewing this thread