Phpcms V9 Phpsso Unable to communicate solution (Phpsso cannot communicate indirectly affect PHPCMS V9 registered members cannot pass "duplicate name cannot pass")

Phpcms V9 Phpsso Unable to communicate solution (Phpsso cannot communicate indirectly affect PHPCMS V9 registered member cannot pass "duplicate name cannot pass")

In general, most people do this:

Make a virtual environment locally, Install the V9 system with localhost or 127.0.0.1, there is no problem in local communication, then make a local data backup, when the remote installation will be installed through the domain name, and then directly restore the local data to the remote server, this situation often occurs SSO and V9 system can not communicate

because the data link in the backup is saved by the URL is localhost or 127.0.0.1 or native 192.168.xxx.xxx, inconsistent with the domain name, such as SSO corresponds to www.lanrensc.com, And the V9 system after recovering the data corresponds to localhost or 127.0.0.1, the inconsistency of course can not communicate, this is one of the most common reasons, generally according to the official method can be solved.

of course, if you find that the official methods can not be solved, it is estimated that you use the local V9 under the directory of all the source code directly to cover the remote, including because of the installation of the V9cache and SSO cache, to know that the local and server cache records in the database information is not the same, In particular, the Linux system is strictly restricted, so even if it is officially provided, it is usually not able to communicate.

reason two: the native V9 cache and SSO cache overwrite the server's corresponding file, which is the second most common cause of the inability to communicate, you can try to modify several files in the cache:system.php and database.php under the \caches\configs\ and \phpsso_server\caches\configs directories, the method of the specific modification does not repeat, you can see caches in the configuration file datebase.php whether it is their own needs of data.

In addition to the above two reasonsThere are two possible ways:
First, if it is a Linux server, the permissions of the site directory are not set, which may cause communication
second, wear www and no www two domain name at the same time point to a server, when installing V9, if it is not with the top-level domain to install, and this machine is usedWww.lanrensc.com, this situation will also fail to communicate

especially the second reason, a lot of people may have overlooked! There is no belt Www,sso think is two different applications, different applications of course is unable to communicate ...

to avoid V9 and SSO problems, it is recommended that you do this:
1, if you do not restore the local data to the server, directly upload the template file, do not overwrite the remote cache folder
2, if the machine has data to restore to the server, save the native data remember not to save the table containing the three prefixes of v9_admin, V9_member and V9_sso, the remote installation of V9 with a new installation, after the installation is complete only upload \caches\bakup\ SQL backup and template packages in the Default\ folder
3, remember, a lot of times, with www and not with Www,sso think is two different applications, even if both point to the same server. If your main use of WWW, remember to use it to install V9.
4,linux Server, please note that the installation of V9 directory permissions, FTP upload please use binary upload, if the server is a standalone host, you have root authority is not recommended to use root privileges of the account upload, but with the establishment of the site when the associated account upload V9 program.

re-provide a way to resolve SSO communication problemsis:
Create a data backup of a table that does not contain the three prefixes of v9_admin, V9_member, and V9_sso (this is not a matter on the local or server), and then install a new V9 on the server (with the install in the latest V9, The cache and Phpssoserver directories overwrite the folder with the same name on the server and delete the Install.lock file in the cache, ensuring that the newly installed V9 communication is successful so that the previous backup can be restored.

