java.lang.IllegalArgumentException: protocol = http host = null

The error message `java.lang.IllegalArgumentException: Repository: cannot add mbean for pattern name *:*` indicates that there's an issue with adding a Management Bean (MBean) to a repository because the specified pattern is invalid or too broad (`*:*`). This typically occurs when trying to register JMX beans in Java.

To resolve this issue, you need to ensure that the MBean registration is done correctly and within the allowed scope. Here are some steps to check and modify your configurations:

1. **Nacos Configuration**[^1]:
- Update the Nacos Spring Cloud Alibaba dependency to a version compatible with your Spring Boot version. If using `<dependency>`, make sure to exclude Guava as suggested.

   <dependency>
     <groupId>com.alibaba.cloud</groupId>
     <artifactId>spring-cloud-alibaba-dependencies</artifactId>
     <version>2.2.3.RELEASE</version> <!-- Replace with a suitable version -->
     <type>pom</type>
     <scope>import</scope>
     <exclusions>
       <exclusion>
         <groupId>com.google.guava</groupId>
         <artifactId>guava</artifactId>
       </exclusion>
     </exclusions>
   </dependency>

2. **Spring Boot Parent Version**:
- Ensure that the Spring Boot parent version is compatible with the Nacos dependency you're using. You may need to update it to a version that works well together, such as `2.3.x` or later versions.

3. **MBean Registration**:
- Check if any manual MBean registrations are happening, and verify that they use a valid pattern (e.g., not `*:*`). Avoid wildcards unless absolutely necessary.
- Review your application's configuration files, like `application.properties` or `application.yml`, for any MBean-related settings and ensure they're properly configured.

4. **Logging and Debugging**:
- Enable more detailed logging for `java.util.logging` or `log4j` to get more context on what might be causing the issue.

If you still encounter problems after these adjustments, you can try reaching out to the Spring Boot or Nacos communities for further assistance, as the issue could be related to specific combinations of versions or configurations.