LabraNet has a service outage on 21st of April from 3pm onwards. All the services will not be available during that outage. The duration of outage is not fully known, users should be prepared that the services will not be available between 21st of April 3pm and 22nd of April 8am
The new LabraNet info video has been added. This video can be used as a substitute to the live version, as it may sometimes be difficult to match schedules and also because of social distancing.
The video is accessible from JAMK Panopto at https://panopto.jamk.fi/Panopto/Pages/Viewer.aspx?id=b41acb3a-b88f-498d-9ab6-ace200c9c1be
LabraNet administration is aware of a recent issue in LabraNet VPN after week 9 service migrations. Some Windows 10 clients disconnect immediately or soon after connecting to LabraNet VPN and reconnecting usually does not help. LabraNet administration is focused on fixing this issue but for now the following workaround seems to resolve this issue.
Configure your LabraNet VPN connection to use split tunneling with the help of LabraNet remote access guide. Be sure to configure the additional fix for DNS lookups while you are at it. More details available here https://student.labranet.jamk.fi/windows-10-and-labranet-vpn-issues/ and in LabraNet remote access guide available here https://student.labranet.jamk.fi/wp-content/uploads/2018/10/Remote_access_guide.pdf
//UPDATE Week 10
Rollback of VPN server for now, should work like before.
Due to data migrations some LabraNet services may be unavailable for short period of times during week 9. Migration takes only minutes in most cases but at least the following services will be unavailable for extended periods due to the sheer volume of data:
- gitlab.labranet.jamk.fi and any CI runners
- LabraNet VPN
The new PostgreSQL server is now available (accessible from LabraNet/student/over VPN) at https://postgres.labranet.jamk.fi. The server is running postgres 12.4, and supports TLS but does not enforce it.
Unlike the MariaDB/MySQL servers, you only get one database, but you can create more schemas inside that database as needed.