I can't log in to a service
If you are unable to connect to a faculty service (or even the faculty website and you are viewing this from another device), try the following steps.
- The requested service is not down: https://status.fi.muni.cz/.
- I can access the FI website (and I don't have to view this page via mobile data).
The FI website is down, Why is the firewall blocking me?
- I log into
I can't log in.
- I am logging into a public faculty service or using a VPN FI.
- I have the correct login, faculty (not secondary) password, and server address.
Problems with SSH, with logging on to computer or to another faculty service.
- Nothing helped →
The following is a more detailed troubleshooting procedure for connection issues.
Your IP address may be blocked by a faculty or university firewall. What to do about it?
- Determine who is blocking you by visiting the university website
- Neither the university website nor the FI website will load → university firewall
- University website loads, but not FI → faculty firewall
- Find out the
public IP address of the problematic device, for example by going to
https://whatsmyip.org or on Linux by running
If you suspect a block by the university firewall, contact the university network administrator:
itQmPwC5CO9@munilpVNY0Wpx.cz. Be sure to provide your public IP address from the previous step as well. If you suspect a block by the faculty firewall, continue on:
- Search for the public address in the faculty blacklist. You must log in to the blacklist page; if this is also a problem, consult the section on logging in below.
- If the address is not on the list, there may be some sort of outage; check https://status.fi.muni.cz again and the availability of the university website.
- If it is there, email
unixXMtdt11Uh@fiZwLuB9f=N.munie1vqdBeiE.czto request an unblock. Be sure to include the public address in question.
- Avoid repeated blocking. See the separate section on reasons for blocking below.
Always authenticate to faculty services with your faculty login and faculty password. You may see xlogin in some materials - it is the same thing.
login typically begins with
x and is either last name
xmach8) or teacher (
The password tends to be a stumbling block. While the faculty password is set to the same as the secondary password (which is how you log in to, say, Eduroam) for fresh students, it remains independent. If you have changed your secondary password, the faculty password is unaffected by the change.
Did you perform remote authentication in IS when you joined FI? If so, the faculty password is probably completely random - the secondary password was not set up in IS when the faculty account was created.
There is also sometimes a problem that the mobile keyboard can add a space at the end when you complete the login.
You can change your faculty password from IS: https://is.muni.cz/auth/system/heslo_fi
To test the accuracy of your information, log in to Faculty Administration with it: https: //fadmin.fi.muni.cz/auth/. If you are successful but not in another service (such as SSH), you can be more confident that the problem is not an incorrect password.
Where are you connecting to? Students are only allowed to connect to Aisu from non-FI networks.* Provide the full machine name:
aisa.fi.muni.cz. See also Remote Access to Services.
How do you log in? Be sure to include your login name, otherwise your client will give you a name that is foreign to Aisa. Typically, the login and machine are listed together, separated by an envelope, for example
$ ssh email@example.com
- I can't type my password! Don't worry, it's just that the client doesn't even display the entered password as asterisks as you might be used to. It's okay, just type the password blindly and confirm with Enter.
*) There are a few other servers available for staff and lab members; however, unless you specifically know about the computer being open to the world, it is not.
If you have tried to log in too many times or on non-public machines, the faculty firewall may have blocked you. The first section describes how to tell and what to do about it.
It's rare that an ISP blocks SSH access. This manifests itself by the connection not being established at all (you won't even be prompted for a password) or crashing soon after it is established. You can verify that this is the case by trying to connect via SSH on port 80 on Anxura. You may not be able to log in (unless you are an FI employee), but Anxur will let you enter the password. You may discover that the provider is blocking port 22 (where SSH normally runs). Unfortunately, we can't advise you to do anything other than contact the provider to ask if they are making fun of you.
As such, if SSH seems to work, logging into Faculty Administration (section above) works, but not to Aisa (or any other computer), you may be experiencing one of the following problems.
Account lockout: you would have received an email about the faculty account being locked out, but you can check your
account summary to be sure. The symptoms are the same as for a wrong password (message
Permission denied, please try again.).
- Exceeded disk quota: you will also get an email about this; you can check this in the Unix login overview, for example
- Too many processes: this can occur if you have recently worked on the machine and have not finished all processes. A common culprit is remote editing in the VS Code editor.
- Broken login configuration: can occur if you have recently changed some of the login scripts. The linked application also allows you to reset the scripts to their default state.
Most often caused by using a secondary password instead of a faculty password, or entering a username instead of a login. See also the list of services using a faculty account.
Other occasional problems include:
- GitLab: use an "LDAP" login. The "Standard" type is only used for external accounts. See GitLab information for more information.
The faculty firewall has assessed you as a potential attacker. Activities leading to such a flagging include:
Attempts to access non-public machines (Nymphs, Aura, Adonis) from an external network.
- This situation can occur, for example, when a laptop is transferred from the FI to the home network, where various programs continue to attempt to contact their former neighbors on the FI network.
- Solution: use an SSH tunnel or a faculty VPN for access. Note that the university VPN is a different service that may not be sufficient for access. See also Remote Access to Services.
Multiple failed login attempts:
- To computers via SSH or remote desktop;
- to a mail server - may be an incorrectly configured email client;
- to Faculty Administration, GitLab, Stratus cloud, etc.
Syncthing software trying to contact your laptop that was previously on the FI network (Eduroam,
wlan_fi) but is no longer, or has been given a different address on Wi-Fi.
- Scanning the ports of faculty computers.
The reality of the Internet, however, is that you do not have to commit the above directly, but someone sharing a public IP address with you does in order for the blocking to occur.
More detailed information about the availability of services from the external network and blocking can be found on the page about restricting access to the faculty network.