# \[Network errors\] - Microk8s **URL:** \ **Category:** microk8s\ **Created:** [May 11, 2021, 2:05pm UTC](https://discuss.kubernetes.io/t/network-errors-microk8s/15865 "2021-05-11T14:05:45Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Zeralls](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/zeralls/32/7613_2.png) [@Zeralls](https://discuss.kubernetes.io/u/Zeralls)\ **Post date:** [May 11, 2021, 2:05pm UTC](https://discuss.kubernetes.io/t/network-errors-microk8s/15865/1 "2021-05-11T14:05:46Z")
Hello, I have been trying to find a solution all day but could not correct the issue so I try asking the community 🙂 I have installed via snap a microk8s cluster with dns addon enabled on my ubuntu 20.04 laptop for testing purposes (v1.21) For some reasons when I try using any curl command from within a pod deployed on this cluster I get an error as follows: curl [https://www.google.com](https://www.google.com) curl: (60) SSL: no alternative certificate subject name matches target host name ‘[www.google.com](http://www.google.com)’ I tried launching a pod with the ubuntu :latest image for debugging purposes and tried running apt-get update -y as the root user. I then get the following error: _oot@test:/# apt-get update -y_ Err:1 [http://archive.ubuntu.com/ubuntu](http://archive.ubuntu.com/ubuntu) focal InRelease 403 Forbidden [IP: 212.95.74.75 80] _Err:2 [http://security.ubuntu.com/ubuntu](http://security.ubuntu.com/ubuntu) focal-security InRelease etc… Reading package lists… Done_ N: See apt-secure(8) manpage for repository creation and user configuration details.\* N: Updating from such a repository can’t be done securely, and is therefore disabled by default.\* etc… It seems like I have Network errors from any pod within the microk8s cluster. I could not figure how to correct this issue. Does anyone have an idea? I would be pleased to provide any further details required. Thank you very much and have a nice day. Christophe ---
**Author:** ![Zeralls](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/zeralls/32/7613_2.png) [@Zeralls](https://discuss.kubernetes.io/u/Zeralls)\ **Post date:** [May 12, 2021, 6:12pm UTC](https://discuss.kubernetes.io/t/network-errors-microk8s/15865/2 "2021-05-12T18:12:06Z")
Just found out that it was my ISP who was rewriting my requests with a suffix domain… I reconfigured my dhcp/settings to ignore the search domain and it works like a charm. The issue is not related to microk8s