AlliedModders - [Release] SourceBans++ (v1.6.4) [Updated: 2021-10-06]

AlliedModders (https://forums.alliedmods.net/index.php)

- SourceBans / SourceBans++ (https://forums.alliedmods.net/forumdisplay.php?f=152)

- - Release SourceBans++ (v1.6.4) [Updated: 2021-10-06] (https://forums.alliedmods.net/showthread.php?t=263735)

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

I didnt have any problems with db, actually the install went very smoothly. Are you sure you used your "panel username" as the prefix for the db name and username.

Example: dbname - prefix_dbname
username - prefix_username

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

I do wish they would add my mods i did a while back to this one day so i dont have to mod it anymore :)

https://forums.alliedmods.net/showpo...&postcount=600

and

https://forums.alliedmods.net/showpo...&postcount=616

Also it looks like in the new release they didnt properly comment out the file header comments as they are being parsed on the admin permissions page.

PHP Code:


		
			
// // SourceBans++ is free software: you can redistribute it and/or modify // it under the terms of the GNU General Public License as published by // the Free Software Foundation, per version 3 of the License. // // SourceBans++ is distributed in the hope that it will be useful, // but WITHOUT ANY WARRANTY; without even the implied warranty of // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the // GNU General Public License for more details. // // You should have received a copy of the GNU General Public License // along with SourceBans++. If not, see . // // This file is based off work covered by the following copyright(s): // // SourceBans 1.4.11 // Copyright (C) 2007-2015 SourceBans Team - Part of GameConnect // Licensed under GNU GPL version 3, or later. // Page: - // // ************************************************************************* if(!defined("IN_SB")){echo "You should not be here. Only follow links!";die();} ?>

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Hi Yes iv Made sure its Correct It iv even made a new database as well to see if that works noithing just says check if the database details are correct

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

As i am going thru this trying to find the comment culpret i will post other things i find.

Such as:

1. Admins.comms.php found issue with presidence of code order.

Current code:

PHP Code:


		
			
global $userbank, $theme; if(!defined("IN_SB")){echo "You should not be here. Only follow links!";die();}if(isset($GLOBALS['IN_ADMIN']))define('CUR_AID', $userbank->GetAid());

I believe it should check for the defined value first as a security measure.
Like so:

PHP Code:


		
			
if(!defined("IN_SB")){echo "You should not be here. Only follow links!";die();}
global $userbank, $theme; 
if(isset($GLOBALS['IN_ADMIN']))define('CUR_AID',  $userbank->GetAid());

2. I believe the comment parsing on the page issue is because they used

PHP Code:


		
			

// ***** and so on for their comment. 

//where

/*  this is a comment valid comment */  
// this is also a valid comment  

//but the way they did this, they mixed the two ways which confuses the server

//the server sees forward slash start and thinks its a comment and then it sees a start forward 
//slash and thinks its the end of the comment. And this is why its parsing it.

so what i will do to test this is do the following: i will change all 53 files that have this type of
defined value in the following way and see if it corrects the issue. Because so far im not finding
any issue with the files other than this.

Its easier to just change the * to #

PHP Code:


		
			

// #######################################################################
//  This file is part of SourceBans++.
//
//  Copyright (C) 2014-2016 Sarabveer Singh <[email protected]>
//
//  SourceBans++ is free software: you can redistribute it and/or modify
//  it under the terms of the GNU General Public License as published by
//  the Free Software Foundation, per version 3 of the License.
//
//  SourceBans++ is distributed in the hope that it will be useful,
//  but WITHOUT ANY WARRANTY; without even the implied warranty of
//  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
//  GNU General Public License for more details.
//
//  You should have received a copy of the GNU General Public License
//  along with SourceBans++. If not, see <http://www.gnu.org/licenses/>.
//
//  This file is based off work covered by the following copyright(s):  
//
//   SourceBans 1.4.11
//   Copyright (C) 2007-2015 SourceBans Team - Part of GameConnect
//   Licensed under GNU GPL version 3, or later.
//   Page: <http://www.sourcebans.net/> - <https://github.com/GameConnect/sourcebansv1>
//
// ###############################################################################

i will keep you posted. :)

3. pages/admin.edit.server.php - Admin edit server file has the div at the top of the file, php tag should always be the very first thing in line 1

original code

PHP Code:


		
			
<div id="admin-page-content">
<?php  
// *************************************************************************
//  This file is part of SourceBans++.
//
//  Copyright (C) 2014-2016 Sarabveer Singh <[email protected]>
//
//  SourceBans++ is free software: you can redistribute it and/or modify
//  it under the terms of the GNU General Public License as published by
//  the Free Software Foundation, per version 3 of the License.
//
//  SourceBans++ is distributed in the hope that it will be useful,
//  but WITHOUT ANY WARRANTY; without even the implied warranty of
//  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
//  GNU General Public License for more details.
//
//  You should have received a copy of the GNU General Public License
//  along with SourceBans++. If not, see <http://www.gnu.org/licenses/>.
//
//  This file is based off work covered by the following copyright(s):  
//
//   SourceBans 1.4.11
//   Copyright (C) 2007-2015 SourceBans Team - Part of GameConnect
//   Licensed under GNU GPL version 3, or later.
//   Page: <http://www.sourcebans.net/> - <https://github.com/GameConnect/sourcebansv1>
//
// *************************************************************************

if(!defined("IN_SB")){echo "You should not be here. Only follow links!";die();}

should be like this

PHP Code:


		
			
<?php  

// #######################################################################
//  This file is part of SourceBans++.
//
//  Copyright (C) 2014-2016 Sarabveer Singh <[email protected]>
//
//  SourceBans++ is free software: you can redistribute it and/or modify
//  it under the terms of the GNU General Public License as published by
//  the Free Software Foundation, per version 3 of the License.
//
//  SourceBans++ is distributed in the hope that it will be useful,
//  but WITHOUT ANY WARRANTY; without even the implied warranty of
//  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
//  GNU General Public License for more details.
//
//  You should have received a copy of the GNU General Public License
//  along with SourceBans++. If not, see <http://www.gnu.org/licenses/>.
//
//  This file is based off work covered by the following copyright(s):  
//
//   SourceBans 1.4.11
//   Copyright (C) 2007-2015 SourceBans Team - Part of GameConnect
//   Licensed under GNU GPL version 3, or later.
//   Page: <http://www.sourcebans.net/> - <https://github.com/GameConnect/sourcebansv1>
//
// ###############################################################################

?>

<div id="admin-page-content">

<?php

if(!defined("IN_SB")){echo "You should not be here. Only follow links!";die();} 

//and then the rest of the php follows

4. Preference only - i dont like it when they use . for name separators instead of _ in file names. Example: name.name.name.php its better to use name_name_name.php

5. I hope they remember when they rewrite this script that "if all you have is PHP in your file" then "you do not need the closing php tag". This will prevent some header loaded issues from the past.

6. OK after going through most of the files in several directories and replacing the header text with new text, i finally found the issue with the parsing of the header comments with some nifty detective work. Seems the dev was just too lazy, he said so himself in the file. I can understand being too tired or too frustrated or too wacky because of coding stress, im a programmer as well. But "LAZY" i cant stand for, its just a poor excuse and does not set a good example at all.

Anyway here is the code.

Its in pages/admin.edit.group.php

It begins right at line 79

Original Code:

PHP Code:


		
			
<?php echo str_replace("{title}", $name, @file_get_contents(TEMPLATES_PATH . "/groups.web.perm.php")) ;?>
<br /><?php }elseif($_GET['type'] == "srv"){?>
<h3>Server Admin Permissions</h3>
<?php  $permissions = str_replace("{title}", $name, @file_get_contents(TEMPLATES_PATH . "/groups.server.perm.php")) ;
echo $permissions;

// Group overrides
// ALERT >>> GROSS CODE MIX <<<
// I'm far to lazy to rewrite this to use smarty right now.
$overrides_list = $GLOBALS['db']->GetAll("SELECT * FROM `" . DB_PREFIX . "_srvgroups_overrides` WHERE group_id = ?", array($_GET['id']));

?>

So to explain whats happing is that he echos (prints out) the full content of the other PHP file - which also includes the php tags. When he echos that value the server has to process (or not) the extra php tags that dont belong, so it parses the comments from the other php file because thats what its told to do basically.

So the solution would the be include the value file but strip out the php tags in the file. So rather than rewrite this all over again lets just patch what is already done here.

Here is the fix:

For this part original code

PHP Code:


		
			
echo str_replace("{title}", $name, @file_get_contents(TEMPLATES_PATH . "/groups.web.perm.php")) ;

lets do this instead, might as well stick with his process, it cant get any worse lol

New Code:

The easiest thing to do is just to remove the header content from this one (included file) content value and "define" statement and just open and close the php at the top of the file file right away. Since the rest of the file "pages/groups.web.perm.php" is all html then thats ok. We will just have to move some php tags around in our pages.admin.edit.group.php file to accomadate it.

for the pages/admin.edit.group.php file change this part:

This is from line 76 to 80 exactly as it is in the original

PHP Code:


		
			
<?php if($_GET['type'] == "web")
{?>
<h3>Web Admin Permissions</h3>
<?php echo str_replace("{title}", $name, @file_get_contents(TEMPLATES_PATH . "/groups.web.perm.php")) ;?>
<br /><?php }elseif($_GET['type'] == "srv"){?>

cut those lines out and add this in its place:

PHP Code:


		
			
<?php 

if($_GET['type'] == "web")
{

echo "<h3>Web Admin Permissions</h3>";

$filevalue = str_replace("{title}", $name, @file_get_contents(TEMPLATES_PATH . "/groups.web.perm.php")) ;

echo $filevalue;

echo "<br />";
 
}elseif($_GET['type'] == "srv"){

?>

Then for the pages/groups.web.perm.php file change this: (remember i changed mine to # sign rather than stars *... ) just in case it does not look the same as yours.

PHP Code:


		
			
<?php

// #######################################################################
//  This file is part of SourceBans++.
//
//  Copyright (C) 2014-2016 Sarabveer Singh <[email protected]>
//
//  SourceBans++ is free software: you can redistribute it and/or modify
//  it under the terms of the GNU General Public License as published by
//  the Free Software Foundation, per version 3 of the License.
//
//  SourceBans++ is distributed in the hope that it will be useful,
//  but WITHOUT ANY WARRANTY; without even the implied warranty of
//  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
//  GNU General Public License for more details.
//
//  You should have received a copy of the GNU General Public License
//  along with SourceBans++. If not, see <http://www.gnu.org/licenses/>.
//
//  This file is based off work covered by the following copyright(s):  
//
//   SourceBans 1.4.11
//   Copyright (C) 2007-2015 SourceBans Team - Part of GameConnect
//   Licensed under GNU GPL version 3, or later.
//   Page: <http://www.sourcebans.net/> - <https://github.com/GameConnect/sourcebansv1>
//
// ###############################################################################


if(!defined("IN_SB")){echo "You should not be here. Only follow links!";die();} 

?>

to this: (the only change your making is to the top of the file ONLY!)

PHP Code:


		
			
<?php 
?>

NOTE: since the other file checks for the defined value then unless someone loads this file directly (which they should not) then youll be fine leaving the define out of this file and just having the html.

That should patch it just fine. Now the edit groups page will load without the nasty parsed comment.

Enjoy :)

After thought: youll have to do the same probably with the two server admin files and the two server files as well in the group management page. I just did the first option for the web admin groups, but i see the others have the same issue.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Dusty just create a simple php file with some connection code inside, and test the connection manually. Do you know how to do that? If not ill help you, is there anything right now in your error log file in the root

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

I added some patch work above in case anyone is interested :)

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Any chance that SBPP++ 2.0 is available for preview, for developers, theme creators, and etc. I want to see what changed in the backend and prepare for it :P

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Request features for SB++ 2.0 here: https://github.com/sbpp/sourcebans-p...-requests-faq/

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

*UPDATE*

Removed error-report post from this thread, and added case on Github instead:

https://github.com/sbpp/sourcebans-pp/issues/228

Sorry, for the off-topic.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by dustydevil (Post 2494152)

thank you

Did you ever work out what was wrong? I'm having the same error as you right now, if i install stable it wont allow me to connect with correct mysql details (logged in through ssh, could access everything fine.) and if I install dev branch from github, I just get a white screen on 'http://mydoma.in/bans/' (not loading the index.php file, if i try to manually go to http://mydoma.in/bans/index.php and use ?debug=1 i still get nothing, and the favicon disappears).

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Errors :

Code:

L 03/10/2017 - 08:05:17: SourceMod error session started

L 03/10/2017 - 08:05:17: Info (map "de_dust") (file "errors_20170310.log")

L 03/10/2017 - 08:05:17: [SM] Exception reported: invalid handle 0 (error: 4)

L 03/10/2017 - 08:05:17: [SM] Blaming: SourceSleuth.smx

L 03/10/2017 - 08:05:17: [SM] Call stack trace:

L 03/10/2017 - 08:05:17: [SM]   [0] IsEndOfFile

L 03/10/2017 - 08:05:17: [SM]   [1] Line 265, SourceSleuth.sp::LoadWhiteList

L 03/10/2017 - 08:05:17: [SM]   [2] Line 86, SourceSleuth.sp::OnPluginStart

L 03/10/2017 - 08:05:17: [SM] Unable to load plugin "SourceSleuth.smx": Error detected in plugin startup (see error logs)

L 03/10/2017 - 08:05:21: Error log file session closed.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by m22b (Post 2502278)

Errors :

Code:

L 03/10/2017 - 08:05:17: SourceMod error session started

L 03/10/2017 - 08:05:17: Info (map "de_dust") (file "errors_20170310.log")

L 03/10/2017 - 08:05:17: [SM] Exception reported: invalid handle 0 (error: 4)

L 03/10/2017 - 08:05:17: [SM] Blaming: SourceSleuth.smx

L 03/10/2017 - 08:05:17: [SM] Call stack trace:

L 03/10/2017 - 08:05:17: [SM]   [0] IsEndOfFile

L 03/10/2017 - 08:05:17: [SM]   [1] Line 265, SourceSleuth.sp::LoadWhiteList

L 03/10/2017 - 08:05:17: [SM]   [2] Line 86, SourceSleuth.sp::OnPluginStart

L 03/10/2017 - 08:05:17: [SM] Unable to load plugin "SourceSleuth.smx": Error detected in plugin startup (see error logs)

L 03/10/2017 - 08:05:21: Error log file session closed.

Are you able to post the contents of "errors_20170310.log"?

Cheers,

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

I'm having a real had time installing, the only error I get occurs during "Step 2 - Database Details". After entering my information correctly (I have been trying to get this to work for weeks now, all the information is correct) I continue to get the error:

Code:

There was an error connecting to your database. 

Recheck the details to make sure they are correct

If anyone could guide me in the right direction or help me out with this problem I'd be really greatful

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by ItsReigN (Post 2505870)

Code:

There was an error connecting to your database. 

Recheck the details to make sure they are correct

If anyone could guide me in the right direction or help me out with this problem I'd be really greatful

FOUND THE ISSUE my MySQL pass had characters that made php read the pass wrong. If you're getting this, remove special characters from the password of the user you're using for sourcebans and it might fix it.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

SourceBans++ now has a Discord Server!

https://discord.gg/gYrkmdt

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Finally, I got SourceSleuth to work properly. If anyone is still having problems with it, you can recompile the source file by moving:

Before:

To:

After:

Afterwards, you must delete the old configs that has to do with SourceBans++ and restart your servers in order to load new ones.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by cravenge (Post 2509978)

Finally, I got SourceSleuth to work properly. If anyone is still having problems with it, you can recompile the source file by moving:

What was the issue you were having? I'm assuming whitelisted users weren't able to connect without getting caught?

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by blackhawk74 (Post 2510008)

What was the issue you were having? I'm assuming whitelisted users weren't able to connect without getting caught?

Kind of, it's just not doing its function as it was supposed/intended to be.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Using latest version 1.5.4.7 .
My sourcebans++ just have been hacked today.
The hacker somehow bypass my admin user / send rcon command to kick all players out of my servers with a greeting message "DOPE RULEZ". Rename all servers to DOPE GOD ...
He also deleted all bans record and all admins users.
I've tracked his IP > from Turkey

I'm here to notice all people who using this.
The hacker seems very similar to sourcebans system.

/// P/s:
I've found out how he can do that ! ...
Fixed

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Care to share how this happened so other owners here can protect themselves?

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by blackhawk74 (Post 2511314)

Care to share how this happened so other owners here can protect themselves?

Sure, currently if we add some one as admin, without password. Hacker can easily login to the sourcebans website even we didn't set that admin as the webadmin role.
You can test on your sourceban now,
just enter the admin username - don't need to enter any password.
Bang
you've have logged in as a website admin...

That's how my site got hacked :\ ...
He'd looked into my sb banlist and test each user until he found one server root admin that I've set without password to log on the website
(my server roles > mod > smod >root and webADMIN is for the sourcebans login )

RIP me.

But I've fixed anyway. Thanks him for that.
If someone here using this and used to set admins in the server without web login password. YOU SHOULD FIX

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by nguyenbaodanh (Post 2511316)

Sure, currently if we add some one as admin, without password. ~
just enter the admin username - don't need to enter any password.
Bang
you've have logged in as a website admin...
~
If someone here using this and used to set admins in the server without web login password. YOU SHOULD FIX

I can reproduce this :/

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by shanapu (Post 2511322)

I can reproduce this :/

Same, but only if we add the user through Sourcebans itself. We have our own built store/admin system, which places users directly into the correct tables. By doing that I can't reproduce...

Some serious leak indeed...

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

This should've been temp "fixed" in a more recent commit, the patch fix was only allowing login through steam, so the manual user login/password boxes are removed.

Edit: Here's the commit from almost 1 year ago: https://github.com/sbpp/sourcebans-p...f66c9b3618589a

Adds this option: http://i.imgur.com/U4d0eC9.jpg

You guys should definitely update asap, there have been some security fixes since, such as this important one.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by blackhawk74 (Post 2511364)

Any instructions to use the steam login one?

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by nguyenbaodanh (Post 2511453)

Any instructions to use the steam login one?

I would just download + replace all files from the latest commit.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

I just used this MySQL query to temp fix the logins for now until it's fixed.

Code:

UPDATE sb_admins SET 'password' = replace('password', '1fcc1a43dfb4a474abb925f54e65f426e932b59e', '');

It'll give you this error box when you try and login

http://i.imgur.com/dXaTier.png

However you'll need to manually wipe new users of their passwords until it's fixed.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by blackhawk74 (Post 2511463)

I would just download + replace all files from the latest commit.

Do you mean from the Dev version? (1.5.5-dev)

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by JackHammer20 (Post 2511510)

Do you mean from the Dev version? (1.5.5-dev)

Or stable version, yes.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by Cooky (Post 2511513)

Or stable version, yes.

I've updated to the dev version, and when logging in with Steam OpenID, it loops back to the front page without logging in?

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Need urgent help with the above, completely locked myself out

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Managed to get logged in as my session was still stored on my phone, so I got normal logins re-enabled, but the Steam Open ID login still loops

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by JackHammer20 (Post 2511520)

Managed to get logged in as my session was still stored on my phone, so I got normal logins re-enabled, but the Steam Open ID login still loops

No issues with the latest stable one. Try that.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Today updated to 1.6.0-git0
Problem with OPENID
If specify the path to the site in the config, 404 appears after logging in.
Wrong URL //bans.my_site/bans.my_site
The path to the site is duplicated

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by MFS (Post 2511526)

Today updated to 1.6.0-git0
Problem with OPENID
If specify the path to the site in the config, 404 appears after logging in.
Wrong URL //bans.my_site/bans.my_site
The path to the site is duplicated

That's probably why I cant login either...

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Registration works.
If after an 404 error simply enter into the browser
Bans.my_site, you will be registered

However, why it issues a double url, I do not understand.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

edit, was just wrong server.

Re: [RELEASE] SourceBans++ (v1.5.4.7) [Updated: 2016-04-28]

Quote:

Originally Posted by Robin955 (Post 2511769)

after removing access to myself on a server, i still have admin there.
sm_rehash is an unknown command
-win10 - csgo
hue hue... easy to remove admin access now! yeah impossibru.

sm_reloadadmins... or mapchange...

Re: [RELEASE] SourceBans++ (v1.5.4.2) [Updated: 2016-03-09]

But the solution

Quote:

Originally Posted by arne1288 (Post 2402820)

Unless you provide a full URL, the URL will be relative, starting from the path you enter into your browser.

E.g. if you are on https://www.example.net/sourcebans/ and you set an URL of

Code:

define('SB_WP_URL','nevvy.pl/sourcebans');

then the links that are based on SB_WP_URL will lead to

Code:

https://www.example.net/sourcebans/nevvy.pl/sourcebans

Use this one:

Code:

define('SB_WP_URL','http://nevvy.pl/sourcebans');