after AWS instance size change, no longer working

[John Kullmann Scheinberg]

My sandstorm has been up and running great over 4 years. i've been able to stop and start it just fine over the years. 

today, i changed the size of my AWS instance and restarted and now I can't reach it. when i go to my xxxx.sandcats.io in my browser it just spins for awhile and then says ''can't open page''

I can ssh in using my xxxx.sandcats.io name so I know it's up and running and dns is fine but I don't see anything bad in the logs and have no idea why or what to do

help?

thanks

[Jacob Weisz]

Can you confirm that changing the AWS instance size didn't do anything like close any firewall ports that were open to Sandstorm? IIRC, AWS blocks inbound web traffic by default.

--

  Jacob Weisz

  goo...@jacobweisz.com

--

You received this message because you are subscribed to the Google Groups "Sandstorm Development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sandstorm-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sandstorm-dev/e087739d-eace-48ae-a04c-1ae506cf3896n%40googlegroups.com.

[John Kullmann Scheinberg]

that's an excellent idea except that I can ssh in so I think the ports are all still open. i will double check though.

[John Kullmann Scheinberg]

yes, just changing the instance size doesn't effect any of the networking or firewall rules that are in effect for that instance. too bad, that would have been an easy fix.

so, I still don't know what's wrong

[John Kullmann Scheinberg]

So, i changed the instance size back to what it has been for the last 4+ years (t2.medium) and I still can't get to it.

so clearly this is some side effect on the AWS side. however, I don't see how it can be a firewall issue as I can still ssh in and port 22 (along with the sandstorm ports) are open and in the firewall rules

sigh

[John Kullmann Scheinberg]

got this fixed, it was  http vs https issue