Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Setting up hostname freeze while onboarding v2.3.5 #1206

Closed
irockbot opened this issue Feb 5, 2024 · 6 comments
Closed

[BUG] Setting up hostname freeze while onboarding v2.3.5 #1206

irockbot opened this issue Feb 5, 2024 · 6 comments

Comments

@irockbot
Copy link

irockbot commented Feb 5, 2024

Describe the bug
After v2.3.5 cp update, when i try to setup hostname onboarding through setup wizard and click start configurations, the progress bar stuck at setting up hostname message forever. I skipped rdns check since i host my mail from gsuite.

Screenshot 2024-02-05 164502

Note: i have checked the hostname A record and rdns PTR records! Everything is fine.

Expected behavior
It should complete the wizard.

Operating system:
Centos 7

CyberPanel version:
2.3.5

@usmannasir
Copy link
Owner

Centos 7 is not supported any more, but can you share main log file content ?

@irockbot
Copy link
Author

irockbot commented Feb 6, 2024

@usmannasir Please find the attached main cp log. Centos 7 working well with cp, no issues so far. I see EOL of centos 7 maintenance is June 2024. We are planning to migrate to Almalinux 8 or 9.
cpmainlog.txt

hassanhashmey pushed a commit that referenced this issue Feb 6, 2024
@usmannasir
Copy link
Owner

can you upgrade and try now ?

@irockbot
Copy link
Author

irockbot commented Feb 6, 2024

@usmannasir Yes now it works! I confirm this fixes the settingup hostname freeze issue. But couple of old issues after upgrade still not solved.

  1. [BUG] imunifyav does not run after upgrading CyberPanel everytime #1098 - even after you give permissions to imunifyfolder, you have to reinstall imunify360 again through cyberpanel UI by entering licence key
  2. Once hostname ssl completed, it will replace the already installed custom sectigo ssl with letsencrypt ssl. I recall you said it won't replace if there is a ssl already. I have to manually install custom ssl again.

@usmannasir
Copy link
Owner

I will close it, you can create seprate issues with more details.

@irockbot
Copy link
Author

irockbot commented Feb 6, 2024

Ok thank you @usmannasir. Please reopen #1098 and provide fix in your next commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants