Author | Message | ||||
---|---|---|---|---|---|
Lord_Zero Ametuar Posts: 122 | Here you can report bugs, crashes and any other problems related to HeXHub. Please specify the version of HeXHub you are running, conditions that may cause the error and debug info if you have (debug info from drwtsn32.log helps). | ||||
Timisoreanul Clone Posts: 9 | Helou , a litell bug: I set Forbid in private messaje the word test [01:22:28] <timi> helou this is a test for hex hub [01:22:28] *** User went offline [01:22:28] <Hub-Security> Error in message/command "|" the op chat: [01:22] <Hub-Security> Fake share/client detected from timi 82.XXX) - Error in message/command "|" Forbiden word in private message : test=replaceall if I put test=replace X or notify or kick works...if i put replaceall i get that error :( | ||||
Lord_Zero Ametuar Posts: 122 | New version of HeXHub will have this error corrected. However, using forbid for private messages is not a good idea. If someone is trying to PM spam the hub, with default settings that person won't be able to "inform" more than 2 users about the new hub or website etc. Without forbid for private messages, 2 friends can share links in private without being kicked for it or their messages replaced or ignored, and users cannot spam the hub. | ||||
Timisoreanul Clone Posts: 9 | Lord_Zero you are right, i test the HeXHub_v3.09 a try to spam te private mesage whit the word " test" end the op chat inform me once | ||||
CrazyGuy n00b Posts: 32 | Me and Nillan have encountered troubles with reconnecting to HexHub 3.11 This hub runs on our server and Nillan was connected to it. After she restarted her computer, she got this.
However, when i tried from my computer, i seen the following
This happens pretty often and only closing the hubsoft and restarting it solves it. Maybe it has to do with the reconnection period set in the hub ? Although a computer restart should be long enough to pass that period in my opinion. :?: | ||||
InfErnuS n00b Posts: 28 | I have one problem in my hub... After some time, the opchat of the hub was not showing anything. I even set some things to see if the changes show up in opchat. I tried restarting the hub and nothing occurred. I realized afterwards that changing the opchat name solved the problem... When I set the opchat name back to its original name, it didn't work. It only worked with another name. I had this happen in a hub of a friend of mine also who didn't have any no-break spaces or normal spaces in the OpChat nick. So that eliminates the possibility of it being a space in the nick that's causing this problem. I also noticed another error which is of the same nature:
But after closing the hub and opening it again, I was able to open the port again. | ||||
Ashura Unstopable Posts: 370 | erm i dont see opchat bot very often, when i refresh userlist or reconnect its there again, but i think its client issue... | ||||
ATAG n00b Posts: 12 | there is a little problem with prefixes...
hub corrects my [HU] prefix to [HU} | ||||
Chucky n00b Posts: 22 | Greetings.... I'm trying to change to Hexhub and i am using last version of it 3.19... As a plugin i'm only using lua plugin and dbgconn2... The thing is that hapenned allready several times the HexHub aplication close by it self... Just desapears, close, finish, puff... and no, it's not hiden... Someone told me that this version as much bugs on it and that i should try an older version :? | ||||
Ashura Unstopable Posts: 370 | try run the hub without plugin for sometime to see if it will happen again | ||||
InfErnuS n00b Posts: 28 | In particular i remember you telling me you were running with Meka][Meka's LUA plugin... i suggest you try running the hub without it and see results.. | ||||
Chucky n00b Posts: 22 | It's not really a bug, but i have been notice that some ip ranges on country codes are not right... I mean....some ranges, the Hub is setting the wrong prefix... Is there a way to update it ? Or should we create a topic to declare the missing ranges, so that can be updated on next release ? | ||||
Lord_Zero Ametuar Posts: 122 | Version 3.22 has instructions on how to update GeoIP database (Help\geoip_update.txt) | ||||
ahile n00b Posts: 18 | AppName: hexhub.exe AppVer: 4.0.1.1 ModName: msvcr80.dll ModVer: 8.0.50727.163 Offset: 00014e9a for info. click here ... C:\DOCUME~1\lAUr\LOCALS~1\Temp\3757_appcompat.txt this is a exemple of erore , end my hexhub have 5 erors at least :-?? , every 10 h i restart my hub :| i don't want to change hexhub soft 1 at day !! hmmm so verli is the best , hexhub next :( | ||||
ahile n00b Posts: 18 | port problem . it say "Error.Listening port is in use" but this port is not in use. I change the port and the problem is not solved. ri must restart the pc or change the HeXHub to \ solved the problem. If i put the port in use on the soft Ynhub or PatokX it works 2 problem in one night withe HeXHub [ and my users or gone ] :roll: | ||||
Lord_Zero Ametuar Posts: 122 |
As i see the error is in msvcr80.dll not in HeXHub. HeXHub is written in asm not in c++ and msvc*.dll are required only for programs that are written in c++. The info you posted is not about a crash caused by HeXHub. | ||||
ahile n00b Posts: 18 | put the server ip under Local Address when you start the hub sorry :oops: | ||||
Lord_Zero Ametuar Posts: 122 | MSVC libraries are used by LUA Plugin so if you want to use it update it with last version from sourceforge | ||||
andreya Clone Posts: 2 | Hello First of all, I'm not a programmer, please have mercy if I wrong something. I have HexHub4.00b running and I notice if registered users use !password command to update their password, something strange is occur: If the new password is shorter than the old one, result is a combination of these two password: the shorter+rest of the old password. I must say, in this condition, the account become useless, and the registered users banned for wrong password. I tried this on 3.21, 4.00b, 4.01 version. All have the same problem. I hope the next release fix this problem. Good luck and keep doing great job | ||||
Lord_Zero Ametuar Posts: 122 | About changing passwords, i found the error and i corrected it. Version 4.02 will be released next week and will have that error corrected. Thanks for reporting it. |