Tony

Administrators
  • Content count

    2,370
  • Joined

  • Last visited

  • Days Won

    143

Tony last won the day on May 22

Tony had the most liked content!

About Tony

  • Rank
    CEO

Profile Information

  • Gender
    Male
  1. Our Amsterdam location was unavailable for a short period of time but right now we have plenty of capacity and can easily now add capacity as necessary. You should see an option to order hosting in that location. For the actual migration it's typically best you disable features that there is user input as information will get out of sync. What users typically do is order hosting and then disable their forums, forms etc. and ask for our team to migrate the site. Once our team has migrated the site the user enables the features again on our systems. Then any new data is only added to our systems. Along with that if your host uses cPanel we can migrate accounts in just a few hours typically (unless the host is slow or blocks backups). So you don't even need to worry about domain changes if you don't want to. Your sites sound fine in a shared environment so you shouldn't need to worry about that aspect. They'll be very fast on our servers, I have no doubt about that.
  2. At this time it's not possible to change the configuration of memcached.
  3. We switched from utilizing randomized ports for users to using a unix socket on user accounts. Any application that supports Memcached should allow for unix sockets the same way it can use ports. You'd use the address: unix://(socket location we give you) We'll have someone from our team update the image to reflect the unix socket change. We missed that while updating the blog post to mention it's handled using sockets.
  4. Hello, I can't make any guarantees on this but maybe this will put you in the right direction. We utilize Litespeed and I've seen a few ways thrown around on how to do this: <FilesMatch "\.(gif|png|jpe?g|svg|svgz|ico|webp)$"> SetEnvIf Origin ":" IS_CORS Header set Access-Control-Allow-Origin "*" env=IS_CORS </FilesMatch> <FilesMatch "\.(ttf|ttc|otf|eot|woff|font.css|css|woff2)$"> Header set Access-Control-Allow-Origin "*" </FilesMatch> So in this case they're doing it for specific types. There is also a discussion on the Litespeed forums on other ways to accomplish this: https://www.litespeedtech.com/support/forum/threads/header-set-access-control-allow-origin.8346/
  5. You'll need to create an email account to send from then since you're not using the mail() function then you're probably best to utilize a mailing library. Here are a few examples of them: http://swiftmailer.org/ https://github.com/PHPMailer/PHPMailer If it's a third party application a lot of them already can interface with SMTP. You just need to tell them the SMTP server and a username and password.
  6. Based on the deepstream installation instructions you'd require your own server so it would not be possible to deploy it on a shared hosting account.
  7. Looks like a similar solution to phpbb where they refer to the php memcached extension as Libmemcached. As for checking if it's working you'd be best to open a ticket. Although for most applications if it's not working they typically end up hanging or throwing an error.
  8. Looking at that guide they are installing the memcache extension not the memcached extension. Unfortunately I don't foresee us offering it as an option after PHP 5.6 just due to the fact it was last updated in 2013: https://pecl.php.net/package/memcache . I don't foresee us offering the memcache extension in PHP 7.0 or 7.1 simply because even our vendors (cPanel, CloudLinux) are not doing it.
  9. The problem is it is utilizing the memcache extension which is only available until PHP 5.6. I'd suggest contacting Xenforo and seeing if there is a way for it to utilize the memcached extension which would be necessary if you're running PHP 7.1.
  10. In that case if you're comfortable with SSH what I recommend doing is we kill the current memcached instance and then start it back up. So if you login to SSH you can run: ps axu | grep memcached Then you should see something like this: 607 802829 0.0 0.0 66600 940 ? Sl 11:07 0:00 /usr/bin/memcached -B ascii -m 64 -s /home/memcachedtest/.hostdata/memcached.sock You'll then want to kill the process so in my case I'd run kill 802829 Then if you do another ps axu | grep memcached you should no longer see the memcached instance running. You will then want to turn it back on in cPanel then hopefully this time around it's operating properly.
  11. Our DNS servers are remote so if the web server goes down then DNS would be served. We also utilize anycast for our DNS infrastructure and have DNS servers in numerous diverse locations. We do this for performance and redundancy purposes.
  12. Our original setup was over IP/Port but had switched it to socket and updated our documentation. I updated the text description for that as well now and we'll see about just updating the pictures as well. As for the issue at hand I'd suggest opening a ticket if you still cannot connect to the memcached socket as the code there shows it supporting it. So it's possible the memcached instance on your account is not starting up properly or something similar.
  13. The reason we do not offer a traditional IP/port is because anyone on the same server as you could read your memcached data. This would be a security risk which is why it's a socket that exists only inside your own accounts Cage meaning only you can access it. I want to clarify one thing the recommended extension is memcached and not the memcache extension. The memcached extension is actively developed: https://pecl.php.net/package/memcached The memcache extension is not: https://pecl.php.net/package/memcache The last release is almost four years ago. Looking at their code directly I believe we can make this work with sockets. What you can do is use the following: unix:///path/to/memcached.sock The reason I'm coming to this conclusion is $this->memcached->addServer(trim($parts[0]), trim($parts[1])); They are calling the PHP extension and the documentation for addServer is here: http://php.net/manual/en/memcache.addserver.php and it accepts sockets on the host and you set the port to 0. That should make everything work when you utilize the Memcache extension in PHP 5.6. Unfortunately looking through the phpbb forums there is no support for the memcached extension meaning you cannot utilize PHP 7.
  14. You don't need to bother throwing up an index but it really doesn't hurt uploading an empty index.html file so it's not a directory listing when you visit the site.
  15. The short answer is the new subdomain will be seen on the web and it'll work fine. The long explanation is: The idea of a public_html folder is really an old way of thinking. The web server is capable of showing a site regardless of the folder it is in. As a result of this cPanel now automatically places any new subdomains/addon domains below your public_html folder. It allows for easier organization and makes so you don't have a case of the content of one subdomain/domain loading from the primary domain of the account also. You can also be even more flexible and do things like: blogs/domain.com blogs/domain2.com forums/domain.com forums/domain2.com