Hiring someone to fix voting

[MarkElf]

After updating the server I manage to 1.13.2, voting broke a few weeks ago. I've spent that time trying endlessly to fix it without luck. The host, shockbyte, is absolutely terrible with providing support so I'm reaching out to any system administrator interested in trying to resolve this. I do want to note that when using the server's ip in nuvotifer it fails to bind to the server's ip, but using 0.0.0.0 seems to be okay. I've been told that this shouldn't happen normally when using nuvotifier - hopefully this provides some insite on the issue.

Please note that I am simply 'middle manning' this transaction as this is for the server I manage. The owner of the server will be paying you once the task is complete. I can assure you that he will pay.

Discord will be given upon contacting me via private message. I'm not interested in any service teams or anyone with a poor reputation.

Edit: I really appreciate the responses, though it seems clear that the best course of action is to switch hosts.

Start up log: with 0.0.0.0:
[14:55:14] [Server thread/INFO]: [Votifier] Enabling Votifier v2.4.2-SNAPSHOT
[14:55:14] [Server thread/INFO]: [Votifier] Loaded token for website: default
[14:55:14] [Server thread/INFO]: [Votifier] DEBUG mode enabled!
[14:55:14] [Server thread/INFO]: [Votifier] Receiving votes over PluginMessaging channel 'nuvotifier:votes'.
[14:55:14] [Votifier NIO boss/INFO]: [Votifier] Votifier enabled on socket /0.0.0.0:6812.

With # ip in config:
16.11 22:37:17 [Server] INFO Loaded token for website: default
16.11 22:37:17 [Server] INFO DEBUG mode enabled!
16.11 22:37:17 [Server] INFO Receiving votes over PluginMessaging channel 'nuvotifier:votes'.
16.11 22:37:17 [Server] INFO Reload was successful.
16.11 22:37:17 [Server] ERROR Votifier was not able to bind to {}

Constant between both start-ups:
[14:55:16] [Server thread/INFO]: [VotingPlugin] Enabling VotingPlugin v5.16.1
[14:55:16] [Server thread/INFO]: [VotingPlugin] Enabled VotingPlugin 5.16.1
[14:55:16] [Server thread/WARN]: [VotingPlugin] No vote has been recieved from minecraft-mp.com, may be an invalid service site. Vote on the site and look in console for a service site, if you get nothing then there is an issue with votifier
[14:55:16] [Server thread/WARN]: [VotingPlugin] No vote has been recieved from www.planetminecraft.com, may be an invalid service site. Vote on the site and look in console for a service site, if you get nothing then there is an issue with votifier
[14:55:16] [Server thread/WARN]: [VotingPlugin] No vote has been recieved from minecraftservers.org, may be an invalid service site. Vote on the site and look in console for a service site, if you get nothing then there is an issue with votifier
[14:55:16] [Server thread/WARN]: [VotingPlugin] No vote has been recieved from minecraftserversorg, may be an invalid service site. Vote on the site and look in console for a service site, if you get nothing then there is an issue with votifier

 

[MarkElf]

Bungee'd server or?

It's a single server. No bungeecord.

 

[MarkElf]

Would help if it was 1.8x but 1.13 is a nogo for me.

Good luck!

There shouldn't be any difference as nuvotifer supports 1.13.2 and acts the same regardless of version but okay.

 

[MarkElf]

Change your IP in votifier to your server's actual IP, not 0.0.0.0, as it sends the local IP to the site.

I included what happens when I do that in the original post a few minutes ago.

16.11 22:37:17 [Server] INFO Loaded token for website: default
16.11 22:37:17 [Server] INFO DEBUG mode enabled!
16.11 22:37:17 [Server] INFO Receiving votes over PluginMessaging channel 'nuvotifier:votes'.
16.11 22:37:17 [Server] INFO Reload was successful.
16.11 22:37:17 [Server] ERROR Votifier was not able to bind to {}

 

[Grumble]

i had this problem before, I believe shockbyte's vps port has to be open to allow votifier to ping the websites, but then again I haven't done it in awhile.

 

[MarkElf]

Does Shockbyte run Docker?

According to a quick Google search and someone on reddit, yes.

 

[MarkElf]

I can fix voting sites, feel free to pm me.

Nothing personal but I have a hard time trusting someone who joined less than a week ago.

Seems like a networking problem with docker, they gotta bind the ip and the port to your server.
If you downgrade your server, would it still work?

I've tried downgrading to 1.13.1, if that's what you mean, and the sever seems to enter a bootloop (didn't look too hard into it). No issues with upgrading. I assume that I would have to open a ticket and ask for them to bind the ip and port with Docker? Assuming that isn't going to work - given how terrible shockbyte support has been so far and every time I've reached out to them - I'll probably just try to convince the owners to switch hosts as I strongly dislike shockbyte and multicraft with a passion.

 

[Jacks]

If you'd like I can try to give it a shot. I haven't used votifier in a while, but I know how it generally works and functions. If you don't trust me that's fine (I know I have no reputation), and if that's the case, I wish you the best of luck in figuring it out!

Additionally, I can test your exact setup and configuration if you allow me to "clone" your server files over onto the host I work at and see if I can confirm it's a Shockbyte issue and not a configuration issue.

Good luck, and have a great day!

 

[UElitez]

Hello,

We're very sorry to hear about your poor experience with Shockbyte.
We provide this kind of support with our hosting plans at no extra cost (with an average response time of 1-8 hours) if you're interested: https://clovux.net/mc

We can help you transfer your files etc.

 

[Wqrld]

It should be bound to 0.0.0.0 as the container doesn't know about the real ip (if it's actually in docker), your host will have to open up the ports for you though. Contact me on discord if you want (Wqrld#7373)