I have been testing out a ubuntu instance on GCS for the last couple weeks and a possible home for one of our web servers. Last week suddenly everything stopped working. I was not able to SSH to shell, and I couldn't even visit the site anymore through my browser. I logged into the dashboard and nothing seemed wrong. I had several other colleges try to go to the site and it loaded without any issues. I could not find any settings in the dashboard that would suggest some kind of block like this, so i assumed I must have triggered some kind of anti spam system. I decided to give a few days before trying to mess with it any further. after 6 days of not messing with it at all I still can not visit the site, or login via SSH.
Then to verify they are blocking my IP address and that it wasn't just something wrong with my machine. I switched my IP and then everything started behaving as expected once again. I can get to the site in my browser and can once again SSH into the VM. After switching back to my previous static IP everything went back to not letting me view the webpage, or ssh into the server.
My problem is that this isn't a permanent solution for me. I have many servers that only allow login from my previous IP address so I'd rather fix the issue with this VM rather then change all those system to allow from a new IP address. Any help on finding the solution would be greatly appreciated.
Please let me know if I can provide any additional info to help find the problem.
followup info:
The way our network is set up the IP we get from DHCP is the real world IP our device is seen with (I think we own a block or something)
this is the first time i've done anything with a GCS VM
Edit: added additional information
Related
Everyday I log into my SSH session of a Google Cloud VM I maintain (Debian).
Since a week ago, I noticed my performance was lagging as I typed into the VM or when doing something else. I mostly login into this VM to check log files of scheduled scripts I have, and even when I use "cat script.log", what used to take less than 2 seconds now takes at least 5 or 7 seconds, loading the log text.
Pinging different websites bring me an reasonable 10 - 15 ms. I'm pretty sure it's not about my local connection either, everything else I do works fine in my local computer.
A warning started to appear now into my session, saying
"Please consider adding the IAP-secured Tunnel User IAM role to start using Cloud IAP for TCP forwarding for better performance. Learn more Dismiss"
I've already configured the IAP secured tunnel to my account, which is the owner account of GCP project.
Another coworker of mine is being able to access the VM without any performance issues whatsoever.
Your issue is in my opinion with the ISP. For some reason the SSH sessions are lagging.
That's why even other computers using your home ISP lag SSH sessions too. If that was firewall rule interfering you wouldn't be able to connect at all.
You may try to reset all the network hardware in your home and if that doesn't help
run tracert command in windows shell and then contact your ISP and pass your findings. It's possible it's something on their end (and if not maybe their's ISP etc).
To solve the problem you need to add "IAP-secured Tunnel User" at the project level in IAM for that user.IAP-secured Tunnel User + See instructions here in a blog I wrote about this. That should solve your problem.
This question asked by coderss but restarting the computer seems to noneffective.
422
The change you requested was rejected.
Make sure you have access to the thing you tried to change.
Please contact your GitLab administrator if you think this is a mistake.
I have above error in Firefox under Linux but I have access in Chromium.
That's looks like typical cookie problem.
I tried clear all Gitlab related cookies then restarted computer without any new sign in attempt. and restarted computer :) yeah I just try
But still same error, same browser.
How can I handle this problem?
This error also occurs at forgot password section and in private tab of Firefox.
Is there another Gitlab related cookie?
The issue should be fixed not only with cookies as discribed, but also with a correction of time system.
I faced exactly the same problem: unable to connect with Firefox, even with a reset of cookies, but I was able to connect with Chrome. (That sounds strange because my clock system was false even on Chrome.)
The solution came with this very short explanation:
"it's was because my local time zone wasn't set up properly (and was messing with cookies)"
Source: https://www.reddit.com/r/gitlab/comments/cv7pov/422_error_on_wwwgitlabcomuserssignin_and/ey7l7lz?utm_source=share&utm_medium=web2x&context=3
This was followed by issue 35447 and issue 40898.
The last one included:
Ok, I suspect the issue here for many people is that the GitLab session cookie is set to Secure here: https://gitlab.com/gitlab-org/gitlab-ce/blob/9c491bc628f5a72424b82bb01e2457150bf2e71c/config/initializers/session_store.rb#L25
Setting the right SSL headers fixes the problem.
If, for some reason, the connection doesn't appear to be an HTTPS connection, Rails won't send a cookie, and the client won't be able to login. You may be able to confirm this by checking the response headers in the GET /users/sign_in endpoint: if you see a _gitlab_session cookie being sent the first time you load the page, then things are working properly.
And:
JuKu
JuKu #JuKu ยท 1 year ago
Solution for HaProxy:
Add these line to your frontend: reqadd X-Forwarded-Proto:\ http
After this change, it worked for me.
See also: https://www.digitalocean.com/community/tutorials/how-to-implement-ssl-termination-with-haproxy-on-ubuntu-14-04
That would avoid the dreaded:
But it depends on the type of GitLab used (gitlab.com or an on-premise GitLab, and the type of Web server used)
For example, issue 53085 refers to issue 54493:
The group had internal availability, while one of it's projects was public (not the one I was having so much trouble with, which was private).
Making the group public solved the problem.
The OP maxemilian reports in the comments it is working now with Firefox on Manjaro:
I checked my updates diary, but only zoom matches between Firefox access time successfully.
I pretty sure this was related to GitLab login code. Suspicious dates (Jan 6- Jan 21 and Feb 3- Feb 6).
I think This update done by GitLab the dates between Feb 3- Feb 6.
In my case, server time was late and I had to change the time, then restart the server and reconfigure the gitlab.
Change server time
sudo timedatectl set-time "06:24:00"
sudo timedatectl set-time "2020-04-23"
sudo hwclock --systohc
Reconfigure Gitlab.
sudo gitlab-ctl reconfigure
Empty Cache and Hard Reload on chrome will do the trick
In my case I was trying to fetch changes using a Git command and also got this error. It turned out that I was using the wrong URL. The .git suffix was missing. Curiously it worked the first time.
For me it was the VPN. If you are connected to a VPN set to a different timezone, turn it off, clear the cookies and you should be able to connect.
I finally decided to run a chainlink node on kovan, so I followed this link https://www.youtube.com/watch?v=t9Uknfw27IU&list=LL&index=8&t=555s on how to set up the node and after a few hours of work I made it happen. So after SSH tunneling into localhost:6688 I got the GUI for the chainlink operator and wrote in the password and got in.
So the next day I decided to program some jobs on the node and did the same thing as last day and got the
site can`t be reached - ERR_CONNECTION_RESET when SSH tunneling in localhost:6688 and I can see that the CL node is running in the linux box with no errors and note I dont own a router.
What I tried so far:
-switching browsers
-temporarily disabled the windows firewall
-manually opening up the port 6688
-deleting the VM instance on Google cloud platform and creating a new one
-double checking the .env file if database and other info from GCP and infuras
WSS were correct
-check the proxy settings
-cleared browser history and cookies
-deleted Winsock catalog entries
None of this has helped to resolve this issue, any help or suggestions would really be appreciated...
Managed to fix the issue myself, If anyone has the same error try this: go to your GCP and go to VM istances - firewall and add an exception for port 6688, then copy the externalIP , add it as your localhost= externalIP :6688...worked for me.
I recently installed Norton Antivirus on my Azure VM. As soon as I did, I lost my RDP connection. Now I'm not able to RDP into my VM. I saw this message in my portal:
So I took a look at my inbound rules and saw the following:
I'm not exactly sure how to read this. Is the DenyAllInBound rule preventing me from connecting to my VM? If so, I didn't add this. Something added it and I cannot remove it. Can someone suggest what I need to do to fix this connection issue?
The deny all rule is not something you can remove. It is also the highest rated rule which means it will be applied after all other rules. So looking at your NSG configuration you do have it setup correctly.
Seeing as you had access to your VM and after installing Norton you do not, it is safe to assume Norton is the issue. From past experience it is likely that Norton modified the firewall rules inside the VM which is not blocking traffic.
Start with this doc: https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshooting/troubleshoot-rdp-connection
It goes over the basic steps to start troubleshooting RDP issues.
If Norton is the cause, you will likely want to look into this doc which uses serial console to correct the RDP keys inside the VM
https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshooting/troubleshoot-rdp-general-error
I had this same problem and seen you post this. I just fixed mine and thought it might help you as well. I was trying all types of different things but Going into your RDP Rule try changing the source port range to something different. When I changed mine to a * instead of putting numbers it actually worked and I was able to get in. Took me forever to figure that out. However I am running a linux Vm with ubuntu.
I have problem signing into Microsoft account from my local account on my machine. This used to be my work laptop I have bought it after I left company. I could sign in on my domain user without any problems. Since I left domain I lost this account.
I am trying to "Sign in with Microsoft account instead" option in Accounts->Your info. After I enter my Microsoft account credentials and insert my local user password I get message "Oops something went wrong. Whatever happen it was probably our fault". Good one Microsoft.
Also similarly when I try to add account to Calendar app I end up with same problem, but here I got more information: "You will need the internet for this. It doesn't look like you're connected to the internet. Check your connection and try again. 0x800704cf". This led me to check Network troubleshooter and this error came up:
Your computer appears to be correctly configured, but the device or
resource (www.microsoft.com) is not responding
Contact your network administrator or Internet service provider (ISP)
Completed Windows can't communicate with the device or resource
(www.microsoft.com). The computer or service you are trying to reach
might be temporarily unavailable.
I have tried many ways how to fix this. (Flush DNS, reboot router etc..), but I am pretty sure that my problem is not with my internet connection. It works perfectly fine, also note that I was able to check this with 2 internet providers with same result. Also another thing is, that this works perfectly fine with other devices in our household.
For me it looks like system don't see microsoft.com. Only thing I am able to work with is One drive.
I am pretty sure I would be able to fix this by resetting Windows 10, but I don't want to loose my installed programs (and licenses).
Any advice will be appreciated. I really ran out of options.
After doing many many thing, only thing that helped was resetting PC. It always does help.