Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 25
  1. #11
    Juriën's Avatar :(){ :|: & };:

    Join Date
    May 2010
    Country
    Posts
    4,064
    Thanked
    2,460
    Thanks
    1,164
    Originally Posted by Cobra View Post
    The port 8080 is blocked on my router/modem. Your statement is invalid ;_; and why would the chatbox be on port 8080 not just 80?
    Because the chatbox server written in node.js is running on port 8080.
    The chatbox connects to the server by sockets.io on port 8080.

    if the port is not open on your computer, you can't communicate with the server.
    Could you atleast show me it's not open on your router?

    proof of port 8080:


    see the; chat.freestylersworld.com:8080 ?
    You can even check it and see the beta version of the chatbox.

    Enough said.
    Last edited by Juriën; 03-26-2014 at 01:07 AM.

  2. #12
    Cobra's Avatar :>

    Join Date
    Feb 2013
    Posts
    2,334
    Thanked
    460
    Thanks
    521
    Originally Posted by King Haze View Post
    Because the chatbox server written in node.js is running on port 8080.
    The chatbox connects to the server by sockets.io on port 8080.

    if the port is not open on your computer, you can't communicate with the server.
    Could you atleast show me it's not open on your router?

    proof of port 8080:
    http://puu.sh/7JutZ.png

    see the; chat.freestylersworld.com:8080 ?
    You can even check it and see the beta version of the chatbox.

    Enough said.
    Interesting, but I think it has nothing to do with the port. More like some sort of javascript issue or the code itself (which I doubt it is). When running a website within the port 8080, most of the routers/modem accept those ports. See, I couldn't see the chatbox as this user posted in here, changing to another different web browser did the fix.

    For Freestyle GunZ upcoming updates and ideas, support and news/information visit:
    Linear88 Blog (Click!)




    Signature by George.

  3. #13
    Juriën's Avatar :(){ :|: & };:

    Join Date
    May 2010
    Country
    Posts
    4,064
    Thanked
    2,460
    Thanks
    1,164
    Originally Posted by Cobra View Post
    Interesting, but I think it has nothing to do with the port. More like some sort of javascript issue or the code itself (which I doubt it is). When running a website within the port 8080, most of the routers/modem accept those ports. See, I couldn't see the chatbox as this user posted in here, changing to another different web browser did the fix.

    http://uploadffs.nl/images/2014/03/25/BSx2z.png
    even then, the script is written in pure javascript/jquery, shouldn't be a browser problem.
    http://socket.io/#browser-support

    These are just up to date browsers, if it wouldn't work, update your browser.

    Firefox:



    Chrome:


    IE:


    mobile works too.
    Last edited by Juriën; 03-26-2014 at 01:17 AM.

  4. #14
    Cobra's Avatar :>

    Join Date
    Feb 2013
    Posts
    2,334
    Thanked
    460
    Thanks
    521
    Originally Posted by King Haze View Post
    even then, the script is written in pure javascript/jquery, shouldn't be a browser problem.
    http://socket.io/#browser-support

    These are just up to date browsers, if it wouldn't work, update your browser.

    Firefox:
    http://puu.sh/7Jv9Q.png


    Chrome:
    http://puu.sh/7JvbH.png

    IE:
    http://puu.sh/7Jveb.png

    mobile works too.
    Thinking about it, could be a connection issue as well. Due to the fact that when I experienced this issue, I could see the chatbox (GUI) itself, however I couldn't receive or send messages at all (request(s) reject). Could be a client issue (web browser) or the one you mentioned, but so far the fix we could find is to change/update your browser (Dave mentioned that).
    For Freestyle GunZ upcoming updates and ideas, support and news/information visit:
    Linear88 Blog (Click!)




    Signature by George.

  5. #15
    Juriën's Avatar :(){ :|: & };:

    Join Date
    May 2010
    Country
    Posts
    4,064
    Thanked
    2,460
    Thanks
    1,164
    Originally Posted by Cobra View Post
    Thinking about it, could be a connection issue as well. Due to the fact that when I experienced this issue, I could see the chatbox (GUI) itself, however I couldn't receive or send messages at all (request(s) reject). Could be a client issue (web browser) or the one you mentioned, but so far the fix we could find is to change/update your browser (Dave mentioned that).
    If there is no message after the input, there is no connection.
    if you are banned, it connects but gives a message.

    Changing browser would be weird, unless it's not up to date.

  6. #16
    Cobra's Avatar :>

    Join Date
    Feb 2013
    Posts
    2,334
    Thanked
    460
    Thanks
    521
    #mysteriousbug.

    I have to go sleep, good night '-'
    For Freestyle GunZ upcoming updates and ideas, support and news/information visit:
    Linear88 Blog (Click!)




    Signature by George.

  7. The following user said thank you to Cobra for this useful post:

    Juriën (03-26-2014)

  8. #17
    McDonald's headquarter

    Join Date
    Jan 2013
    Country
    Posts
    1,587
    Thanked
    716
    Thanks
    1,049
    Originally Posted by Cobra View Post
    #mysteriousbug.

    I have to go sleep, good night '-'
    I still have the same problem

  9. #18
    Squid's Avatar The guy

    Join Date
    Oct 2012
    Posts
    143
    Thanked
    66
    Thanks
    33
    I have had the same problem, just doesn't bother me not having it :p

  10. #19
    Metanova's Avatar No.

    Join Date
    Jan 2014
    Country
    Posts
    189
    Thanked
    30
    Thanks
    35
    Inspect the element by right clicking the chatbox and in the network tab, see what your transfer rate is or if you even have a stable enough connection. If it was debunked that the browser isn't the issue then try at least that.

  11. #20
    Juriën's Avatar :(){ :|: & };:

    Join Date
    May 2010
    Country
    Posts
    4,064
    Thanked
    2,460
    Thanks
    1,164
    Originally Posted by AnnaBoo View Post
    Inspect the element by right clicking the chatbox and in the network tab, see what your transfer rate is or if you even have a stable enough connection. If it was debunked that the browser isn't the issue then try at least that.
    Wouldn't make sense because it's done by socket.io, you won't see any traffic going in and out...

Page 2 of 3 FirstFirst 123 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)