-
Messages (PMs) page navigation links are not working (Page 2, Next, Back, etc)
I installed 5.0.4 beta and that fixed it. Thanks.
-
Messages (PMs) page navigation links are not working (Page 2, Next, Back, etc)
No 3rd party apps or language packs, or themes, etc.
-
-
Messages (PMs) page navigation links are not working (Page 2, Next, Back, etc)
When in personal messages, if there are multiple pages in the PM, when clicking on, say page 2 of the navigation links, it does not take you to page 2 of the PM, but it takes you to the main page of the forum. Example, the link to page to in the PM is the following: https://myforum.com/index.php?/messenger/8120/&page=2 But, the link sends me to the following: https://myforum.com/index.php?%2Fmessenger%2F8120%2F=&page=2 Which is the main page of the forum, not the 2nd page of the PM. Sorry, this is for IC 5.0.3.
-
Moderator CP > IP Tools > IP Address > Posts
This same issue exist in IC 5.03. I assume it was only fixed in 4.x.
-
API errors on new server: IP_ADDRESS_NOT_ALLOWED
Apparently, many machines have multiple IPs configured in the network interfaces. Each virtual host is listening to a specific IP. If there is any networking related action performed by PHP, for example a cURL call, the default IP is used every time. If I set CURLOPT_INTERFACE manually in my PHP script, the correct IP for my virtual host will being used in the call instead of the server's default. For example, you can set the IP by coding in curl_setopt($curl, CURLOPT_INTERFACE, 'xx.xx.xx.xx'); before sending your cURL call to the server. Which is the correct IP address for my website. I guess you could also do curl_setopt($curl, CURLOPT_INTERFACE, $_SERVER['SERVER_ADDR']); which seems to resolve to the IP of the actual website that PHP is running on in lieu of the default IP of the network interface.
-
API errors on new server: IP_ADDRESS_NOT_ALLOWED
That was it! The remote server I am calling from has an IP address of, for example, 12.34.56.79, but the API logs show it as 12.34.56.77, notice it's slightly different. So, it appears as though there is some sort of proxy on the remote server that I'm making the calls from, because 12.34.56.79 is the actual IP of my remote server making the calls, but it is showing up as 12.34.56.77 in the logs. I added the 12.34.56.77 to the allowed IPs and it worked. I still don't understand why it would show up as a different IP, but it worked. I just hope they don't switch the IP again. Can you put in a wildcard, like 12.34.56.*?
-
API errors on new server: IP_ADDRESS_NOT_ALLOWED
It's definitely seems to be an error with the API system and not the server (Apache). When I choose, "No, allow any IP address to make API calls using this key" in the API settings, it works fine. When I try to be more restrictive and select, "Yes, I will specify which IP addresses can make API calls using this key" and add the IP address, it does not work and fails.
-
API errors on new server: IP_ADDRESS_NOT_ALLOWED
API logging is on and the call is reaching the API system, it is giving the 403 Forbidden response code in the API log.
-
API errors on new server: IP_ADDRESS_NOT_ALLOWED
I've double checked. Everything in the ACP is the same as it was before, and I'm making calls from the same exact IP I was before. Nothing is different, except for the new server that I'm making the calls to; but it doesn't appear as though that makes any difference, according to the setup of the API system.
-
API errors on new server: IP_ADDRESS_NOT_ALLOWED
No. Not using CloudFlare Yes. It's in the Allowed IP addresses. No. It's not banned. The IP is in Allowed IP addresses.
-
API errors on new server: IP_ADDRESS_NOT_ALLOWED
I am getting the following error when trying to use the API on my new server. Array ( [errorCode] => 2S290/8 [errorMessage] => IP_ADDRESS_NOT_ALLOWED ) However, I am not making calls from any new IP address that wasn't already in my Allowed IP Addresses list. In other words, I am making calls from the same IP address as I was before I changed servers. Let's say Server A was the older server, and Server B is the new server. Before, my forum was installed on Server A and I was making calls from Server A, everything worked. Now I am making calling from Server A (the old IP) to Server B (the new forum install), and I'm getting this error.
-
Switching Servers, Permission Denied
Thanks! I did not know that.
-
Switching Servers, Permission Denied
After playing around with it, I was finally able to set sql_host to localhost:3306, note I had to include the port for localhost of :3306 to make localhost to work on this server, which is a Plesk server running Almalinux 9, just in case anybody has the same problem. So, in the conf_global.php file looks like 'sql_host' => 'localhost:3306'
-
Switching Servers, Permission Denied
So, after some debugging, come to find out the $INFO{'sql_host'] needed to be 127.0.0.1 instead of localhost. Which is weird. First time I've seen that on a Linux system. I've seen it on a local Windows PC, but not a Linux system. Is there any reason I can't use 127.0.0.1 for the production server, if that's what it's requiring in order to run the script(s)?
-
Switching Servers, Permission Denied
I think it's probably a MySQL connection issue. May be access rights to the database or something. AH01071: Got error 'PHP message: PHP Fatal error: Uncaught IPS\\Db\\Exception: Permission denied in /var/www/vhosts/mywebsite.com/system/Db/Db.php:269\nStack trace:\n#0 /var/www/vhosts/mywebsite.com/system/Db/Db.php(356): IPS\\_Db->_establishConnection()\n#1 /var/www/vhosts/myswebsite.com/system/Db/Db.php(487): IPS\\_Db->checkConnection()\n#2 /var/www/vhosts/mywebsite.com/system/Db/Db.php(972): IPS\\_Db->preparedQuery()\n#3 /var/www/vhosts/mywebsite.com/system/Session/Admin.php(112): IPS\\_Db->replace()\n#4 [internal function]: IPS\\Session\\_Admin->write()\n#5 [internal function]: session_write_close()\n#6 {main}\n thrown in /var/www/vhosts/mywebsite.com/system/Db/Db.php on line 269' I created a simple test file to connect to mysql using the conf_global.php file include('conf_global.php'); $con = mysqli_connect($INFO['sql_host'], $INFO['sql_user'], $INFO['sql_pass'], $INFO['sql_database']); // Check connection if (mysqli_connect_errno()) { echo "Failed to connect to MySQL: " . mysqli_connect_error(); } else { echo "connected"; } exit;and I am getting a similar Permission denied error in my test.php file. AH01071: Got error 'PHP message: PHP Fatal error: Uncaught mysqli_sql_exception: Permission denied in /var/www/vhosts/mywebsite.com/test.php:25\nStack trace:\n#0 /var/www/vhosts/mywebsite.com/test.php(25): mysqli_connect()\n#1 {main}\n thrown in /var/www/vhosts/mywebsite.com/test.php on line 25'I know my conf_global.php file contains the correct information because I can use the same information to log into MySQL at the command prompt without a problem. Some how I can't do it in a PHP script though.