When you migrate a domain from one server to another but leave the original user account intact on the old CWP (CentOS Web Panel) server, you may encounter a 502 Bad Gateway<\/strong> error with “cwpsrv” displayed when trying to access that user’s control panel.<\/p>\n\n\n\n This occurs because the cwpsrv (CWP’s web server) configuration still references the old domain’s proxy settings and backend services that no longer exist on the server. The configuration expects certain services or resources to be available for the domain, but since the domain has been moved, those references become broken, resulting in the 502 error.<\/p>\n\n\n\n CWP uses cwpsrv<\/strong> as its internal web server to handle user panel requests. When a domain is properly hosted on the server, cwpsrv has the correct configuration to proxy requests to the appropriate backend services. However, when you:<\/p>\n\n\n\n The result is a mismatch between what cwpsrv expects and what actually exists, causing the gateway error.<\/p>\n\n\n\n The fix is straightforward: rebuild the cwpsrv configuration for the affected user account. This regenerates the configuration files with the current state of the user’s domains and services.<\/p>\n\n\n\n Step 1: Rebuild the user’s cwpsrv configuration<\/strong><\/p>\n\n\n\n Replace Step 2: Restart the cwpsrv service<\/strong><\/p>\n\n\n\n Step 3: Test access<\/strong><\/p>\n\n\n\n Try logging into the user panel again. The 502 error should now be resolved.<\/p>\n\n\n\n If rebuilding the configuration doesn’t work, here are additional troubleshooting steps:<\/p>\n\n\n\n Ensure the service is running properly.<\/p>\n\n\n\n This lets you see what configuration exists for the user and identify any problematic entries.<\/p>\n\n\n\n Review the logs while attempting to access the user panel to see specific error messages.<\/p>\n\n\n\n If you need immediate access and the rebuild doesn’t work:<\/p>\n\n\n\n This temporarily removes the problematic configuration. You can restore it later or regenerate it properly.<\/p>\n\n\n\n To avoid this issue in the future:<\/p>\n\n\n\n If the user account is no longer needed on the old server (all domains have been migrated), consider removing it entirely:<\/p>\n\n\n\n Or check available removal scripts:<\/p>\n\n\n\n The 502 Bad Gateway error in CWP user panels after domain migration is a configuration mismatch issue that’s easily resolved by rebuilding the cwpsrv configuration for the affected user. The This is a common scenario in server administration when domains are moved between servers, and knowing the quick fix can save significant troubleshooting time.<\/p>\n","protected":false},"excerpt":{"rendered":" Problem Overview When you migrate a domain from one server to another but leave the original user account intact on the old CWP (CentOS Web Panel) server, you may encounter a 502 Bad Gateway error with “cwpsrv” displayed when trying to access that user’s control panel. This occurs because the cwpsrv (CWP’s web server) configuration […]<\/p>\n","protected":false},"author":1,"featured_media":5839,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[11],"tags":[25],"class_list":["post-5838","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nerd-blog","tag-cwp"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/posts\/5838","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/comments?post=5838"}],"version-history":[{"count":0,"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/posts\/5838\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/media\/5839"}],"wp:attachment":[{"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/media?parent=5838"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/categories?post=5838"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/specialmansolution.com\/en-us\/wp-json\/wp\/v2\/tags?post=5838"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Understanding the Issue<\/h2>\n\n\n\n
\n
The Solution<\/h2>\n\n\n\n
Step-by-Step Fix<\/h3>\n\n\n\n
\/usr\/local\/cwpsrv\/htdocs\/resources\/scripts\/cwpsrv_rebuild_user_conf username\n<\/code><\/pre>\n\n\n\nusername<\/code> with the actual CWP username experiencing the issue.<\/p>\n\n\n\nsystemctl restart cwpsrv\n<\/code><\/pre>\n\n\n\nAlternative Solutions<\/h2>\n\n\n\n
Check cwpsrv Status<\/h3>\n\n\n\n
systemctl status cwpsrv\n<\/code><\/pre>\n\n\n\nReview User Configuration<\/h3>\n\n\n\n
cat \/usr\/local\/cwpsrv\/conf.d\/users\/username.conf\n<\/code><\/pre>\n\n\n\nCheck cwpsrv Logs<\/h3>\n\n\n\n
tail -f \/usr\/local\/cwpsrv\/logs\/error_log\n<\/code><\/pre>\n\n\n\nTemporarily Disable User Configuration<\/h3>\n\n\n\n
mv \/usr\/local\/cwpsrv\/conf.d\/users\/username.conf \/usr\/local\/cwpsrv\/conf.d\/users\/username.conf.bak\nsystemctl restart cwpsrv\n<\/code><\/pre>\n\n\n\nPrevention<\/h2>\n\n\n\n
\n
When to Delete the User Account<\/h2>\n\n\n\n
# From CWP root panel: User Accounts \u2192 List Accounts \u2192 Delete\n<\/code><\/pre>\n\n\n\nls -la \/scripts\/ | grep remove\n<\/code><\/pre>\n\n\n\nConclusion<\/h2>\n\n\n\n
cwpsrv_rebuild_user_conf<\/code> script regenerates the proper configuration based on the current state of the server, eliminating references to migrated or removed domains.<\/p>\n\n\n\n