No profiles are available; check internet connectivity and refresh the profile list.

[Shelme74]

I got this problem since yesterday, tried updating and resetting the WebUI with no avail.

[caramel-juni]

I also have this issue ... confirmed server had internet access via it's shell (it can hit package repos).

# apt update
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease                                                      
Hit:2 http://security.ubuntu.com/ubuntu focal-security InRelease                                 
Hit:3 https://deb.nodesource.com/node_14.x focal InRelease
Hit:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Reading package lists... Done
Building dependency tree       
Reading state information... Done
44 packages can be upgraded. Run 'apt list --upgradable' to see them.

Another link suggested upgrading all packages and manually installing jdk kits via the shell. However, when running apt upgrade -y, the process gets stuck around ~50%, so I'm yet to see whether this will help with the issue.

Any known fixes yet?

[caramel-juni]

Okay, just figured out the fix. For some reason, inside my /etc/resolv.conf file, the nameserver was set to nameserver 127.0.0.11.
In order to change this inside the trueNAS shell, I had to install a text editor - in my case apt-get install vim.
Once installed, I then changed the file to hit literally anything else that actually is a nameserver, like 8.8.8.8, so the final modified file was as below:

# Generated by Docker Engine.
# This file can be edited; Docker Engine will not make further changes once it
# has been modified.

nameserver 8.8.8.8
search local
options ndots:0

# Based on host file: '/etc/resolv.conf' (internal resolver)
# ExtServers: [192.168.0.25 94.140.14.14]
# Overrides: []
# Option ndots from: internal

Upon reloading the MineOS webUI, and refreshing the profile list, they populated. Hooray!

[shinyone]

@Shelme74 Can you confirm if this is the same issue and if the fix from @caramel-juni fixes the issue for you?

[kieraneglin]

@shinyone I can confirm that the solution provided by @caramel-juni worked for me!