Chat archive · 2017-06
Narutoxy · Thu Jun 15, 2017 05:46 PM UTC
are you guys using chrome as well?
Narutoxy · Thu Jun 15, 2017 05:50 PM UTC
I get an error saying "support@prohashing.com" address not work ?
Narutoxy · Thu Jun 15, 2017 05:57 PM UTC
anyone had similar issues?
GregoryGHarding · Thu Jun 15, 2017 06:43 PM UTC
@Narutoxy : in the mean time you have alot of mods on your browser and alow of extentions, try disabling some, might be messing with the site
FRISKIE · Thu Jun 15, 2017 08:25 PM UTC
@ GregoryGHarding - Ha! there were other times
GregoryGHarding · Thu Jun 15, 2017 09:33 PM UTC
@FRISKIE : im still waiting for a green name, since steve gave the go ahead for me to mod the forum.. lol
lilbob · Thu Jun 15, 2017 10:24 PM UTC
@GregoryGHarding : grats! get them o
VanessaEzekowitz · Fri Jun 16, 2017 12:03 AM UTC
Good read, Steve. Explains a lot stuff. Greg, kick there asses for us
FRISKIE · Fri Jun 16, 2017 12:50 AM UTC
im still waiting for a green name Grasshopper?
GregoryGHarding · Fri Jun 16, 2017 12:55 AM UTC
my first act as moderator, will be to silence you. lol
GregoryGHarding · Fri Jun 16, 2017 01:21 AM UTC
@FRISKIE : you suck for responding
Forum notification · Fri Jun 16, 2017 02:07 AM UTC
fattygrub · Fri Jun 16, 2017 02:38 AM UTC
loos like its down from here
VanessaEzekowitz · Fri Jun 16, 2017 02:38 AM UTC
Yep seems to be down from here, too. from NH also.
mjgraham · Fri Jun 16, 2017 02:39 AM UTC
yea my awesome fixed order tanked out!
VanessaEzekowitz · Fri Jun 16, 2017 02:40 AM UTC
No sooner do I finally know what I’m doing on NH and get an order that’s doing well...and the pool goes down. just my mazel
(fortunately it’s a "standard" order)... I’m sure the guys will get it going again soon.
Chris Sokolowski · Fri Jun 16, 2017 03:15 AM UTC
Internet connection went out due to storms near the datacenter in Philadelphia. It’s back online and I’m restoring services
webshaun · Fri Jun 16, 2017 03:22 AM UTC
That storm is like 100 miles away from philadelphia near where I live.
GregoryGHarding · Fri Jun 16, 2017 03:27 AM UTC
while youre online steve accepted my "application" to mod the forum, would you give me my permissions?
Chris Sokolowski · Fri Jun 16, 2017 03:27 AM UTC
I’m confused about it too. They said it was due to the storm but it’s nowhere nearby
Chris Sokolowski · Fri Jun 16, 2017 03:27 AM UTC
maybe some trunk line is having issues?
webshaun · Fri Jun 16, 2017 03:28 AM UTC
if the servers are in harrisburg or something, that could be it but if they are in or immediately near philadelphia - storm isn’t here yet
webshaun · Fri Jun 16, 2017 03:37 AM UTC
why not move to azure or aws, or both?
Chris Sokolowski · Fri Jun 16, 2017 03:49 AM UTC
No, the servers are basically in Philadelphia. We don’t want to use cloud hosting because that make the service susceptible to people impersonating us to get access to the servers.
Chris Sokolowski · Fri Jun 16, 2017 03:55 AM UTC
It’s a router issue. I’m talking with the people at the datacenter to fix it remotely.
Chris Sokolowski · Fri Jun 16, 2017 04:00 AM UTC
I can’t access the remote interface, so I need them to reset it in person and enable the remote interface so I can configure it further
GregoryGHarding · Fri Jun 16, 2017 04:11 AM UTC
or you can just let your miner switch pools automatically
VanessaEzekowitz · Fri Jun 16, 2017 04:18 AM UTC
my ASICs switched over to the backup, but NH orders don’t support backup pools :-/
Chris Sokolowski · Fri Jun 16, 2017 05:14 AM UTC
Okay, finally diagnosed our problem.
Chris Sokolowski · Fri Jun 16, 2017 05:15 AM UTC
Verizon changed our static IP address when the router got rebooted. We own 98.115.147-74-78, but now for some reason we have 75-79.
Chris Sokolowski · Fri Jun 16, 2017 05:15 AM UTC
No clue why, but I’ll call them tomorrow
GregoryGHarding · Fri Jun 16, 2017 05:25 AM UTC
make sure no social engineering going on :p
dfair98 · Fri Jun 16, 2017 05:30 AM UTC
Chris Sokolowski wrote: Updating DNS entries for the site what's the TTL?
shyrwall · Fri Jun 16, 2017 05:48 AM UTC
still not changed in the dns
shyrwall · Fri Jun 16, 2017 05:49 AM UTC
new ip is 98.115.147.77 but 3333 seems firewalled. I assume fw-rules has the old ip in them
shyrwall · Fri Jun 16, 2017 05:50 AM UTC
cool. Maybe i will mine alone for a few seconds
AvPro · Fri Jun 16, 2017 05:53 AM UTC
guess it takes some further minutes for everything to come back to life?
Chris Sokolowski · Fri Jun 16, 2017 05:53 AM UTC
ttl is 5 minutes, so should update for most people quickly
Chris Sokolowski · Fri Jun 16, 2017 05:53 AM UTC
ip address changed, so you may need to wait for it to propagate across the internet.
shyrwall · Fri Jun 16, 2017 05:54 AM UTC
When did you change it? Doesnt look live on the dns servers, dig prohashing.com IN A @dns1.registrar-servers.com , shows not changed. And thats independant of the ttl
AvPro · Fri Jun 16, 2017 05:57 AM UTC
we can mine direct to the new IP on port 3333
GregoryGHarding · Fri Jun 16, 2017 06:13 AM UTC
forums went down aain for like 10 mins
AvPro · Fri Jun 16, 2017 06:30 AM UTC
DNS propagation can take 24hrs....no?
FRISKIE · Fri Jun 16, 2017 06:31 AM UTC
Be sure to flush your local DNS cache
FRISKIE · Fri Jun 16, 2017 06:33 AM UTC
@FRISKIE : you suck for responding Don't like the name Grasshopper?
VanessaEzekowitz · Fri Jun 16, 2017 06:35 AM UTC
DNS has propagated for me (I have .77, and whatsmydns.net shows it everywhere too), but the pool is still dead as far as the miners are concerned.
GregoryGHarding · Fri Jun 16, 2017 06:36 AM UTC
FRISKIE wrote: @FRISKIE : you suck for responding Don't like the name Grasshopper? no, u suck for responding, as in youre not good at it
GregoryGHarding · Fri Jun 16, 2017 06:36 AM UTC
VanessaEzekowitz wrote: DNS has propagated for me (I have .77, and whatsmydns.net shows it everywhere too), but the pool is still dead as far as the miners are concerned. homepage is still kaput
AvPro · Fri Jun 16, 2017 06:59 AM UTC
What’s the latest Chris?
VanessaEzekowitz · Fri Jun 16, 2017 07:01 AM UTC
The latest is that something is still b0rk3d.
shyrwall · Fri Jun 16, 2017 07:06 AM UTC
I think its getting ddosed. Massive packetloss. Probably what happened from the start and verizon killed it. Then after dns update ddosed cotinued...maybe? Heh
Chris Sokolowski · Fri Jun 16, 2017 07:08 AM UTC
still having trouble. May be a DDoS, I don’t know
Chris Sokolowski · Fri Jun 16, 2017 07:08 AM UTC
Would make sense that it worked until I updated the DNS records if it was a DDoS
Chris Sokolowski · Fri Jun 16, 2017 07:10 AM UTC
The Verizon IP address thing still is an issue as well
Chris Sokolowski · Fri Jun 16, 2017 07:10 AM UTC
but it shouldn’t be affecting anything right now
shyrwall · Fri Jun 16, 2017 07:34 AM UTC
Yeah i had 0% packetloss, dns record changed and then 80% loss.
Nalith · Fri Jun 16, 2017 07:45 AM UTC
Website still down, any ETA to resolution?
Nalith · Fri Jun 16, 2017 07:47 AM UTC
Might be a good idea to move the solution to something like Azure where you have native DDoS protection...
VanessaEzekowitz · Fri Jun 16, 2017 07:47 AM UTC
whatsmydns.net is showing the site resolving to *.74 again at all sites.
VanessaEzekowitz · Fri Jun 16, 2017 07:48 AM UTC
OVH has good DDoS protection as well. At least, the few times it’s been tried on my little server, they handled it well.
AvPro · Fri Jun 16, 2017 07:50 AM UTC
Will payouts proceed at usual time?
shyrwall · Fri Jun 16, 2017 07:53 AM UTC
Regardless of where to host for ddos protection the pool addr should be different than the main webserver and of course a diff box.
shyrwall · Fri Jun 16, 2017 07:54 AM UTC
Multiple pool addrs would be great with nondisclosed backend ip like most other pools do it
VanessaEzekowitz · Fri Jun 16, 2017 08:17 AM UTC
yup, pool’s deader than 4 o’clock... *looks at clock*... um, deader than 10 o’clock last night?
