I deleted the firewall rule default-allow-ssh and now I cannot SSH via browser window even after adding back the same rule:
I have gone through the check list here, but still can't figure out the cause. The problem is happening to existing instances as well as a newly created Ubuntu f1.micro instance which has all the Google defaults.
What could be wrong?
The default-ssh-allow firewall rule must have tcp:22 as authorized port.
It seems you just set 22, without specifying the protocol. that's certainly the reason.
Related
I am learning to make chrome app which will receive UDP packets from remote device. All works perfectly fine, however, in order to receive packets from remote device I need to turn off windows firewall.
Now the problem is that I do not see a way to add this app to pass firewall exception. Because I only see option to allow Chrome through firewall, not any of its apps.
What is the solution / workaround to this problem?
Thanks
Since I didn't get any answer, the best possible solution I could find so far is to add the port on which my chrome app will listen to firewall inbound rules. I didn't know this was possible until i read this article https://www.thewindowsclub.com/block-open-port-windows-8-firewall
However I still don't consider it the right solution because lets say I publish my app online for other people, it will not be convenient for them to be adding rules to their firewalls.
I am sure there must be a better solution.
I'm trying to set up GUI access to a linux VM on google compute engine. I've followed the advice here:
https://groups.google.com/forum/#!topic/gce-discussion/tN9oZs8xWps
I can get as far as getting the instance to show up on the "My Computers" section of the CRD app, but it is grayed out.
I'm wondering if I need to mess around with firewall settings, or try a different desktop (I've been trying cinnamon). I'd appreciate any help. Thanks!
You definitely have to open the ports to connect, so you will have to use a firewall rule. Cloud Platform has an implicit deny ingress rule. It is explained in the thread you posted that also if you are using CentOS there is an additional steps to disable a firewall rule.
I am using couchbase server , I have opened it and got popup as
"IP address seems to have changed . Unable to listen on 'ns_1#10.0.2.15'"
and after that it is showing error like localhost refused connection.
how to resolve this problem?
and what is exact root cause of this problem?
If this is a Couchbase installation in a developer environment then this is probably a benign issue.
What the error message is telling you is that the IP address that it had previously identified itself as does not appear to be valid any longer (This could happen in a developer environment if your router has given you a new IP). Generally this is a bad thing for a production deployment as if it is part of a cluster then the other nodes will no longer be able to see it.
If it is a single node and nothing external is trying to reach it with a fixed IP then there is no need to worry and there are no issues to be resolved.
I've just auto-deployed a LAMP stack on Google Compute. Before when I did this successfully I had to enable HTTP and HTTPS. Now it seems like they've changed the interface totally again.
And this time I find the options to enable are greyed out.
I tried accessing my phpmyadmin at [ip address]/phpmyadmin and it timed out...so clearly http and https are not being allowed in....
How do I enable HTTP and HTTPS access?
This is what it looks like right now. Not sure where to go from here as the option is totally greyed out.
Ok, the answer is to hit the EDIT button at the top.
I do express the opinion though that this is the most un-intuitive (yet glossy) interface I've ever used.
I suffer no shame!
You can do the following:
Your instance is associated with the default network. Click on the default link.
This will bring to the default network settings where you should review all the Firewall Rules
Check if there are any firewall rules with tcp:80 or tcp:443 present for traffic. This will allow access from outside via http, https. If not, click on Add Firewall Rule and then provide access to those ports.
Alternately, you can also use gcloud to manage your firewall. Refer to gcloud firewall command example here.
My Chrome browser is in a weird state. It claims that it's configured to use a proxy server and that it can't connect to that server. Problem is, when I go to the LAN settings, the option to use a proxy server is deselected. Toggling this setting has no effect.
I've tried reinstalling Chrome but the problem persists.
Any idea on how I can get it to stop trying to use whatever proxy it thinks it's configured for?
try selecting no proxy in network settings of chrome. i'm not sure whether this going to work but it is worth trying. its not going to do any harm.
hope you find a solution