NooBody Posted April 18, 2019 Share Posted April 18, 2019 Hi Guys, OK so really struggling with setting up H2c in the cloud with Azure. Tried with https originally and lets encrypt against the azure name and my own domain name but having issues so decided to try with default 8080 which worked or so I thought..... I've setup the firewall rules on the VM (<vm>-ng see attached screenshot) and also within the Linux VM using firewall-cmd which seemed to work OK (however even stopped the daemon) and have setup the c2 command line as a cron job (@reboot) I can get to the website now with my CNAME alias over 8080 however whenever I enter the details (license, token and new username and password) it flashes up with an error and takes me back to the same screen (attached screenshot). I managed to catch the error as "Your session has expired" which I don't understand as I get this even if I restart all my browsers and the service... Any ideas... getting frustrated now, am sure its an Azure thing but buggered if I know what.... Thanks for your help in advance Cheers Bob Link to comment Share on other sites More sharing options...
NooBody Posted April 20, 2019 Author Share Posted April 20, 2019 Hi Guys, any ideas? Does it need more than port 8080 to establish a session? Firewall ports above have been opened on the Azure Resource group and in Linux with firewall-cmd... @Sebkinne@Foxtrot@Darren Kitchen - any ideas guys at a bit of a loss here? Thanks! Shaun Link to comment Share on other sites More sharing options...
NooBody Posted April 20, 2019 Author Share Posted April 20, 2019 further update opened all ports to my ISP range temporarily in Azure and stopped firewall daemon in Linux still the same so can't be firewall... (no problems with my ssh sessions at all either) Any help appreciated! 🙂 Link to comment Share on other sites More sharing options...
NooBody Posted April 23, 2019 Author Share Posted April 23, 2019 sorted! Was nothing to do with firewall... I performed a tcpdump -vv on both sides and found the error was an invalid token even though I was using the one I set. The problem was down to running the command line in a cron job so it auto restarts on reboot. I've subsequently got rid and run it as a backgrounded process (&) which seems to have done the trick. Cheers Bob Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.