503 Excessive Load Warning - I need to change the default page

General Discussion

Suggested Topics

  • 0 Votes
    8 Posts

    The setting @julian describes belongs to the browser (chrome/chromium in this case), not NodeBB.
    If you're using chrome/chromium, press F12, then F1 to show the options. Check the option and keep the tools open while refreshing the page to ensure the cache is disabled.

  • 0 Votes
    11 Posts


    Thanks for offering help!
    Here is the users_list.tpl content.

    I did change users.js

    <!-- BEGIN users --> <li class="users-box registered-user" data-uid="{users.uid}"> <div class="user-data-container"> <div class="user-media"> <a href="{config.relative_path}/user/{users.userslug}"> <div class="user-picture"> <img src="{users.picture}" /> </div> </a> <div class="user-info"> <span> <i component="user/status" class="fa fa-circle status {users.status}" title="[[global:{users.status}]]"></i> </span> <br/> <!-- IF route_users:joindate --> <div title="joindate" class="joindate"> <i class='fa fa-clock'></i> <span class='timeago' title="{users.joindateISO}"></span> </div> <!-- ENDIF route_users:joindate --> <!-- IF route_users:reputation --> <div title="reputation" class="reputation"> <i class='fa fa-star'></i> <span class='formatted-number'>{users.reputation}</span> </div> <!-- ENDIF route_users:reputation --> <!-- IF route_users:postcount --> <div title="post count" class="post-count"> <i class='fa fa-pencil'></i> <span class='formatted-number'>{users.postcount}</span> </div> <!-- ENDIF route_users:postcount --> </div> </div> <div class="user-info-extended"> <a href="{config.relative_path}/user/{users.userslug}" class="uie-username"><h4>{users.username}</h4></a> <p>{users.signature}</p> <p id="uie-location">{users.location}</p> <a>{users.website}</a> </div> </div> <div class="user-interaction"> <!-- IF !config.disableChat --> <a href="#" class="btn btn-primary btn-sm chat-btn-users" data-uid='{users.uid}' data-username='{users.username}'>[[user:chat]]</a> <!-- ENDIF !config.disableChat --> </div> <hr> </li> <!-- END users -->

    I alse changed the /srv/<url>/www/public/src/client/users.js file content to handle the chat button. That should not alter the new user load but here is the content I added to the end of Users.init = function(){... function.

    /*--- eRes change: added users button listener*/ /* note: delegated event handling*/ $('#users-container').on('click', '.chat-btn-users', function() { app.openChat($(this).data('username'), $(this).data('uid')); }); /*note: hide user interaction div */ $('#users-container').on("mouseenter", '.users-box', function(){ $(this).children(".user-interaction").css('visibility','visible'); }); $('#users-container').on("mouseleave", '.users-box', function(){ $(this).children(".user-interaction").css('visibility','hidden'); }); /*--END-- eRes change: added users button listener */

    Thanks again!

  • 0 Votes
    9 Posts

    We can close this top..

    I'm not realy sure how I fixed it.
    I went into my DNS host changed the domain to another one, tested then switched it back and seems to have shaken something lose in the dns

    Thanks for the help

  • 0 Votes
    5 Posts

    You know (one of) the main difference(s) between TCP and UDP, don't you?

    TCP is connection-oriented, UDP isn't. So there is no UDP core-functionality to check whether the receiver is alive (/has the port opened).

    You'd either need to create server-side code or know the server-behavior (e.g. responses to specific datagrams) to achieve an UDP port-scanner.

    If you're able to write server-side code the best is to ask for UDP port status via TCP since it has reliable data-transfer implemented.

  • 0 Votes
    4 Posts

    @a_5mith Thanks - was looking for that everywhere..