Anyway, we have enabled RSSHub for some of rixCloud infrastructure. Users can obtain rixCloud Telegram Channel and Twitter news through RSS:
rixCloud Telegram Channel RSS
rixCloud Twitter RSS
---
Build your own RSSHub
rixCloud Telegram Channel RSS
rixCloud Twitter RSS
---
Build your own RSSHub
SIP003 / SIP007 integration within rixCloud Networks backend services is completed.
SIP002 / SIP003 / SIP007 Integration for rixCloud RESTful API is still in progress.
We expect to officially support these new features within 60 days.
SIP002 / SIP003 / SIP007 Integration for rixCloud RESTful API is still in progress.
We expect to officially support these new features within 60 days.
In order to fit Surge 3 new features, Surge 2 (also known as Surge Legacy) will not be supported in rixCloud API v2. Till then, the configuration files we distributed will contain a lot of new settings that are not compatible with Surge 2.
It is recommended that subscribers should turn to other softwares or upgrade to the newest version of Surge as soon as possible.
It is recommended that subscribers should turn to other softwares or upgrade to the newest version of Surge as soon as possible.
Google DNS (
Please use another DNS
8.8.8.8 ) is inaccessible in most China Telecom Network at the moment (2018-06-25T07:35Z).Please use another DNS
1.1.1.1 - Cloudflare DNS80.80.80.80 - Freenom World (China Telecom via CN2)208.67.222.222 - OpenDNSWe're planning to support AES-128-GCM/AES-256-GCM/CHACHA20-IETF-POLY1305 in the AEAD algorithm suite, in the near future.
However, the performance on Surge (with current AES-GCM) is still lower than expected, and we're going to look up to this issue.
Public Beta for SIP007 will be released in 30 days.
However, the performance on Surge (with current AES-GCM) is still lower than expected, and we're going to look up to this issue.
Public Beta for SIP007 will be released in 30 days.
rixCloud API v2 is now compatible with SIP003 & SIP007, and will be compatible with SIP002 soon.
rixCloud API v1 will be terminated within 60 days after API v2 is active. Till then, we’ll send email reminders and please update your API URI in time.
Public Beta for AEAD & Simple-OBFS will be released in 45 days.
rixCloud API v1 will be terminated within 60 days after API v2 is active. Till then, we’ll send email reminders and please update your API URI in time.
Public Beta for AEAD & Simple-OBFS will be released in 45 days.
We plan to invite users who use Surge only or those who use the latest original protocols to help us test AEAD features(Initial Beta Stage).
Details will be issued later.
Details will be issued later.
[ATTENTION]
Stripe is currently suspected of being intercepted by UnionPay, some mainland China credit card holders might not be able to pay through our credit card payment gateway. If you are experiencing this issue, please use other credit card or change to other payment gateway instead. BTW, please make sure you have sufficient foreign exchange quota. We are sorry about this.
Stripe is currently suspected of being intercepted by UnionPay, some mainland China credit card holders might not be able to pay through our credit card payment gateway. If you are experiencing this issue, please use other credit card or change to other payment gateway instead. BTW, please make sure you have sufficient foreign exchange quota. We are sorry about this.
Please subscribe rixCloud Status page to get latest incidents and scheduled maintenance notifications.
rixCloud may push notifications to you by Email, SMS, RSS or Webhook.
Visit rixCloud Status (if you’re in China please visit https://status.rixcloud.me instead) to check our current and past network status.
rixCloud may push notifications to you by Email, SMS, RSS or Webhook.
Visit rixCloud Status (if you’re in China please visit https://status.rixcloud.me instead) to check our current and past network status.
rixCloud plans to prohibit users from creating or changing service passwords, but instead generating a random password directly from RANDOM.ORG.
Since we only use pre-generated credentials and API subnoscriptions in most cases, this approach can reduce the problems caused by weak passwords or special characters in service passwords.
Since we only use pre-generated credentials and API subnoscriptions in most cases, this approach can reduce the problems caused by weak passwords or special characters in service passwords.
Tempest TCN via @vote
Do you support us using a random password instead of creating a password by your own?
anonymous poll
Yes, rixCloud! – 118
👍👍👍👍👍👍👍 67%
No. – 59
👍👍👍👍 33%
👥 177 people voted so far. Poll closed.
anonymous poll
Yes, rixCloud! – 118
👍👍👍👍👍👍👍 67%
No. – 59
👍👍👍👍 33%
👥 177 people voted so far. Poll closed.
You can create a new random credential anytime using rixCloud API by simple clicking at our new management portal, which will be integrated with our new API.