View Issue Details

IDProjectCategoryView StatusLast Update
0000026Pax FaxPax Faxpublic2025-06-06 10:08
Reportertitanium Assigned To 
PriorityhighSeverityblockReproducibilityalways
Status newResolutionopen 
Summary0000026: Phaxio api and dashboard no longer exist for new users. They have been assimilated into Sinch.
DescriptionThere is no way to get access to a Phaxio dashboard anymore, it has been moved to the Sinch dashboard now. The api/documentation is now different.
https://developers.sinch.com/docs/fax/v2-v3migration/

Some instructions for the Pax Fax app seem to be similar:
For the "Phaxio API Key" and "Phaxio API Secret" I put the Key/Secret from Sinch.

However, for the "Phaxio Webhook Token" it instructs to go to the Phaxio account, click 'Webhooks' on the left panel, then copy the token found under 'Webhook Token'.
There seems to be no corresponding Webhooks section on Sinch.
Where to get a Sinch webhook that will work with Pax Fax?

Same question goes for the Phaxio Callback URL - what to replace it with?

Much appreciated.
Steps To ReproduceGo to https://developers.sinch.com/docs/fax/v2-v3migration/

If you attempt to register by pressing sign up on https://console.phaxio.com/sf_guard_users/sign_in - it redirects you to https://sinch.com/apis/fax-api/

You can register on the new dashboard here - https://dashboard.sinch.com/signup
TagsNo tags attached.

Activities

DoubleBastionAdmin

2025-04-05 10:02

administrator   ~0000101

I've just tested logging in to phaxio.com and sending and receiving faxes from Pax Fax. Everything works as usual. Existing phaxio.com accounts work as expected with Pax Fax. Yet, what you mention above is perfectly true: when a new customer tries to open a new phaxio.com account, he is redirected to sinch.com and if he signs up for a new account there, he finds a new dashboard, where he can't find many of the fields that existed on Phaxio's dashboard, such as the 'Webhook Token' field.

According to this page: https://developers.sinch.com/docs/fax/v2-v3migration/ it seems that phaxio.com accounts will have to migrate to sinch.com accounts and all the apps that connected to phaxio.com will have to transition to connecting to sinch.com, with all the necessary changes imposed by their API.

Sinch's dashboard loads very slowly and seems unintuitive and Phaxio should have informed their existing customers about the upcoming transition, therefore, I'll have to investigate further and decide if I change Pax Fax to connect to sinch.com, or renounce to phaxio/sinch entirely and connect Pax Fax to other better and cheaper fax provider, such as Telnyx.

titanium

2025-04-06 03:03

reporter   ~0000102

Thank you for taking a quick look.
I see, it's good that it still works for people with existing Phaxio accounts for the time being. That being said, as you have seen, this makes Pax Fax unusable for new people.

I need to let my team know whether we can expect to use Pax Fax in the near future, or whether we need to let go of our idea of using Nextcloud for faxing. For us, it doesn't matter if it will be Telnyx or Sinch, just as long as Pax Fax will begin working. Can you please provide a rough estimate of whether it will take you just a few weeks or perhaps many months to make the modification to the Pax Fax app? That way I can bring something back to my team.

Thanks again!

DoubleBastionAdmin

2025-04-06 13:04

administrator   ~0000103

I've asked Phaxio about this transition to Sinch's API that they didn't announce, and I'm waiting their reply tomorrow.

I remember that Telnyx has discontinued basic authentication for HTTP requests to their API, which makes receiving faxes from them inside Nextcloud impossible. Many years ago, when I chose Phaxio as fax provider for Pax Fax, they were the best provider because they offered reliable services at the cheapest price possible: $2 per month for a phone number and 7 cents per sent and received page. All the other providers, like eFax, myFax, iFax, Fax.Plus etc. had a much higher monthly ongoing cost, like $10, or more. Why should a small business pay $10 or more each month just to be able to send a few faxes per year? Meanwhile, Telnyx added faxing to their voice and SMS services and they became 'the best provider' but as I mentioned, they can't be used to receive faxes inside Nextcloud. So, Phaxio remains a good choice for Pax Fax. Yet, sooner or later all apps will have to transition to Sinch's API. According to this page: https://sinch.com/apis/fax-api/ , a fax page will cost only 4.5 cents, as opposed to 7 cents with Phaxio. A US fax enabled number will cost $0.88 per month, as opposed to $2 per month with Phaxio. So, if Sinch's API is as reliable as Phaxio's and if their dashboard gets a bit faster, Sinch seems actually better than Phaxio.

Since I consider being able to send and receive faxes inside Nextcloud very important, I plan to change Pax Fax to make it support both API's, in the sense that I'll add a new section on the Settings page, where each new user will enter his Sinch credentials in order to use them to send and receive faxes connecting to Sinch's API, while old users will continue to use their Phaxio credentials on the Settings page to send and receive faxes as usual, until they find the time to port their phone numbers from Phaxio to Sinch. Also, the documentation will have to change, to show users where to find the necessary credentials on Sinch's dashboard.

I can't tell exactly how much time the code changes will take, since it also depends on other factors, such as on Sinch's support response time, but it definitely shouldn't take too long. I suppose about two weeks. I'll post a reply on this thread once I finish.

titanium

2025-04-06 14:07

reporter   ~0000104

Great, thank you.
I appreciate the details and that you will attempt to get it done fairly quickly.
We'll be waiting!

Cheers

DoubleBastionAdmin

2025-04-25 06:52

administrator   ~0000105

Last edited: 2025-04-25 06:55

Pax Fax version 1.1.9 has been published. After you upgrade, enter your Sinch credentials on the Settings page. You can test by sending a one page pdf file to your own number. As I was expecting, Sinch support delayed this new version quite a bit.

titanium

2025-04-29 05:05

reporter   ~0000106

Thanks! Will check it out soon.

DoubleBastionAdmin

2025-05-17 08:23

administrator   ~0000111

Have you tried entering your Sinch credentials on the Pax Fax' Settings page and sending a test fax to your number ?

titanium

2025-05-18 16:11

reporter   ~0000112

I was able to test the connection with Sinch, that portion seemed to work, so that's great already.
I am waiting to hear from my colleague who will be testing sending and receiving a fax. I'll let you know as soon as I hear back from him.

Thanks for all this.

titanium

2025-05-29 05:54

reporter   ~0000113

Hi, thank you for your patience, I finally got it setup with the other person from the team.

However, when attaching a file to send, whether by upload or by choosing an existing nextcloud file, a browser alert pops up saying "Error!".
When trying to upload again, it keeps endlessly spinning and saying "uploading".

Is this a known bug?

titanium

2025-05-29 06:28

reporter   ~0000114

Additionally, if I ignore that error and press "Send fax" it says "Error ! Please check your settings !" - although the settings appear to be correct, and I was able to receive a test fax from Sinch.
Probably that error is due to the file upload error.

DoubleBastionAdmin

2025-05-29 09:23

administrator   ~0000115

I can't reproduce your error because everything works fine here. When you try to upload a file from your computer to send it as fax, what error do you see in your Nextcloud log (Administration settings > Logging). Also, after you upload a file, do you see it saved in the "/Pax_Fax/temp_files" folder of your Nextcloud ?

Any details about your Nextcloud installation would be relevant: have you installed it directly on the server, as advised in our guide, or are you using the Docker All-in-One installation ? What web server and what MariaDB version ?

DoubleBastionAdmin

2025-05-29 09:32

administrator   ~0000116

Also, if you log in via SSH to your server and inspect your Nextcloud installation folder, do you see the "pax_fax" directory in "nextcloud_root_directory/apps" or in "nextcloud_root_directory/custom_apps" ? ("nextcloud_root_directory" can be "/var/www/cloud.example.com" or something similar, depending on your setup)

titanium

2025-05-29 12:22

reporter   ~0000117

So, this is what it says:
UnexpectedValueException
FilesystemIterator::__construct(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files): Failed to open directory: No such file or directory

However when I go to All Files>Pax_Fax>temp_files - I do see the folder and the files that I tried to upload.
That being said, our nextcloud is configured to use remote s3 storage. We do not use on-server storage ( as indicated in the /var/www/nextcloud/data/username/files/Pax_Fax/temp_files link).

This s3 connection is properly configured with nextcloud, and we have been uploading and sharing files for a few years now. Perhaps PaxFax doesn't take into account the possibility of a s3 setup?

titanium

2025-05-29 12:26

reporter   ~0000118

To answer your other questions, we have installed nextcloud directly, we are not using docker.
Ubuntu 24.04 LTS.
MariaDB 10.11.11
Nginx

Yes there is a pax_fax folder in /apps

And I double checked - there is no pax_fax folder in nextcloud/data/username/files - because its in s3.

titanium

2025-05-29 12:28

reporter   ~0000119

Here is the related portion of our nextcloud config

  'objectstore' =>
  array (
    'class' => '\\OC\\Files\\ObjectStore\\S3',
    'arguments' =>
    array (
CONNECTION INFO HERE - bucket, key, secret, hostname, port, region, use_ssl, autocreate
    ),
  ),

DoubleBastionAdmin

2025-05-29 14:13

administrator   ~0000120

From your Nextcloud error it's quite clear: the "FilesystemIterator" class, which is used whenever you upload or pick a file to send as fax, cannot operate on the "/var/www/nextcloud/data/username/files/Pax_Fax/temp_files" directory, although the directory exists, because it's not stored on local storage, but, as you mentioned, on remote storage. Your issue is somewhat similar to this issue: https://help.nextcloud.com/t/cannot-share-files-or-folders-with-objectstorage/150931 although I perfectly understand that you can share files and folders in your setup, you just can't upload files with Pax Fax. In fact, the files get uploaded to the "/var/www/nextcloud/data/username/files/Pax_Fax/temp_files" directory, since you can see them there, but you get that popup error and the Nextcloud error with the "FilesystemIterator" class not finding that directory where the files are stored until they are sent as fax.

Please upload a one page pdf file in Pax Fax to send as fax and then, in spite of the popup error, while logged in to your server via SSH, rescan all the files by running:

cd /var/www/nextcloud
sudo -u www-data php occ files:scan --all

Then try sending the fax to your own fax number.

DoubleBastionAdmin

2025-05-29 14:23

administrator   ~0000121

Also, do you have the following line in your '/var/www/nextcloud/config/config.php' file:

'datadirectory' => '/var/www/nextcloud/data',

titanium

2025-05-29 14:29

reporter   ~0000122

Well I can see the files I uploaded to Pax Fax in nextcloud, and that command didn't do anything - 0 folders 0 files 0 new 0 updated 0 removed 0 errors.

This time I tried both selecting an existing file from nextcloud and uploading the file again. And I ran the provided command multiple times.
After pressing Send it says "Error ! Please check your settings !"

Below is the list of errors, starting at the bottom. The first ones are me trying to select an existing file from nextcloud.

Error
index
UnexpectedValueException
FilesystemIterator::__construct(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files): Failed to open directory: No such file or directory

May 29, 2025, 11:23:31 PM


Error
index
Exception
base64_encode(): Argument #1 ($string) must be of type string, false given in file '/var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php' line 554

May 29, 2025, 11:23:29 PM


Error
PHP
file_get_contents(/var/www/nextcloud/data/username/files/Pax_Fax/faxes_sent/Test fax__18553301239_2025-05-29_14-23-28_897470.pdf): Failed to open stream: No such file or directory at /var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php#554

May 29, 2025, 11:23:29 PM


Error
index
Exception
base64_encode(): Argument #1 ($string) must be of type string, false given in file '/var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php' line 554

May 29, 2025, 11:23:29 PM


Error
PHP
file_get_contents(/var/www/nextcloud/data/username/files/Pax_Fax/faxes_sent/Test fax__18553301239_2025-05-29_14-23-28_897470.pdf): Failed to open stream: No such file or directory at /var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php#554

May 29, 2025, 11:23:29 PM


Error
PHP
file_get_contents(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files/Test fax.pdf): Failed to open stream: No such file or directory at /var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php#546

May 29, 2025, 11:23:28 PM


Error
PHP
file_get_contents(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files/Test fax.pdf): Failed to open stream: No such file or directory at /var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php#546

May 29, 2025, 11:23:28 PM


Error
index
UnexpectedValueException
FilesystemIterator::__construct(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files): Failed to open directory: No such file or directory

May 29, 2025, 11:21:38 PM


Error
index
UnexpectedValueException
FilesystemIterator::__construct(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files): Failed to open directory: No such file or directory

May 29, 2025, 11:21:38 PM


Error
PHP
file_get_contents(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files/Test fax.pdf): Failed to open stream: No such file or directory at /var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php#400

May 29, 2025, 11:21:37 PM


Error
PHP
file_get_contents(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files/Test fax.pdf): Failed to open stream: No such file or directory at /var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php#400

May 29, 2025, 11:21:37 PM

titanium

2025-05-29 14:31

reporter   ~0000123

and yes,
  'datadirectory' => '/var/www/nextcloud/data',

is part of the config file

DoubleBastionAdmin

2025-05-29 15:07

administrator   ~0000124

You can also check if your " 'objectstore' => ... " entry in your "config.php" file is similar to the one described in the first post of this issue: https://github.com/nextcloud/server/issues/34407 .

Also, in your Nextcloud database, does your 'oc_mounts' table specify "OC\Files\Mount\ObjectHomeMountProvider" in the "mount_provider_class" column on the row where "user_id" is your username, as suggested in this issue: https://github.com/nextcloud/server/issues/25781#issuecomment-1383091969 ? Or do you see "OC\Files\Mount\LocalHomeMountProvider" in that field ?

DoubleBastionAdmin

2025-05-29 15:24

administrator   ~0000125

From the error you have posted it's clear that some common PHP functions, like "file_get_contents", cannot operate on the path given: "/var/www/nextcloud/data/username/files/Pax_Fax/temp_files/Test fax.pdf". So, the file is there, but the function fails to get the file content. This must be caused by the remote storage you are using. All Pax Fax users who use local storage don't experience this issue. Why do you have a space in your test file name ("Test fax.pdf"). Spaces can create problems in file paths. Please use "test_fax.pdf".

titanium

2025-05-29 15:37

reporter   ~0000126

Yes the entry is similar but not entirely the same.
for example, I have this set to true, instead of false:
      'autocreate' => true,

As for your other question, for all 30 users except for 2 accounts, it was set to "OC\Files\Mount\ObjectHomeMountProvider".
The two accounts which it was set to OC\Files\Mount\LocalHomeMountProvider were the admin user and another user. I was using the admin user account to try faxing, however another user which was also running into the same issues had it set properly to "OC\Files\Mount\ObjectHomeMountProvider".

In any case, I updated the admin user to have it set to "OC\Files\Mount\ObjectHomeMountProvider" yet the same problem persists with the same errors..

titanium

2025-05-29 15:43

reporter   ~0000127

I am guessing this is because it is trying to access the file and folder that does not exist on the server. I understand that this works for people who use local storage, however we don't use local storage, and that is likely the main issue here.
We haven't had any issues with other apps that we use - file uploads, file sharing, realtime file collaboration, forms, deck - everything has been pretty consistent and working good for a few years for all 30 users.

This is the first time we run into an issue related to the fact that we're set up with remote storage. From the data that I have, I assume that the config that we have should be correct, and the programming of this app tries to access the absolute path on the server, instead of the relative path to the remote storage?


By the way, I renamed the file, and its the same problem -

Error
index
UnexpectedValueException
FilesystemIterator::__construct(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files): Failed to open directory: No such file or directory

May 30, 2025, 12:37:59 AM


Error
index
Exception
base64_encode(): Argument #1 ($string) must be of type string, false given in file '/var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php' line 554

May 30, 2025, 12:37:57 AM


Error
PHP
file_get_contents(/var/www/nextcloud/data/username/files/Pax_Fax/faxes_sent/Testfax__12132942943_2025-05-29_15-37-54_720388.pdf): Failed to open stream: No such file or directory at /var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php#554

May 30, 2025, 12:37:57 AM


Error
PHP
file_get_contents(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files/Testfax.pdf): Failed to open stream: No such file or directory at /var/www/nextcloud/apps/pax_fax/lib/Controller/PaxfaxController.php#546

May 30, 2025, 12:37:54 AM


Error
index
UnexpectedValueException
FilesystemIterator::__construct(/var/www/nextcloud/data/username/files/Pax_Fax/temp_files): Failed to open directory: No such file or directory

May 30, 2025, 12:37:49 AM

titanium

2025-05-29 15:51

reporter   ~0000128

from what im reading in the app code it seems to be using the config.php datadirectory parameter, which is

           $datadir = $this->config->getSystemValue('datadirectory', \OC::$SERVERROOT . '/data') . '/';

which means that is is trying to access the data from the directory on the server where it doesn't exist. If I'm correct then perhaps this should account for object storage?
https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/primary_storage.html

DoubleBastionAdmin

2025-05-29 16:01

administrator   ~0000129

So, in your Nextcloud installation, when you go to All files > Pax_Fax > temp_files, you say that you can see there the file that you have uploaded to send as fax: Testfax.pdf. Yet, if you are logged in via SSH to your server and try to open that file by running:

     nano /var/www/nextcloud/data/username/files/Pax_Fax/temp_files/Testfax.pdf

you get "No such file or directory" ?

If this is the case, where does your S3 storage get mounted ?

titanium

2025-05-29 17:00

reporter   ~0000130

Yes, no such directory. It is not mounted on the server like a normal disk, it is remote storage.
Here is a quote from the nextcloud documentation "The Simple Storage Service (S3) backend mounts a bucket on an Amazon S3 object storage or compatible implementation (e.g. Minio or Ceph Object Gateway) into the virtual filesystem."

The files in the s3 storage are not normal files with the same name, which you can access directly. they are converted into files with these names:
urn:oid:10042
urn:oid:11075
urn:oid:10928
urn:oid:10580
urn:oid:11052
urn:oid:1106

Nextcloud manages them via the database, where it keeps record of which of these weirdly named files is responsible for what actual file with what permissions.
Overall, I can summarize that this is expected nextcloud behavior, and I didn't do anything out of the ordinary - I followed official nextcloud instructions and set up remote storage per their documentation. https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/primary_storage.html

The interesting thing is that although the PaxFax app uploads the file into temp_files correctly, and I can see it there before I press send - when I hit send, it gets transferred into the "faxes_sent" directory, however at that point the file loses all data, and becomes a 0kb .pdf

DoubleBastionAdmin

2025-05-29 17:32

administrator   ~0000131

Ok, I think I'll replace the "FilesystemIterator" class and the "file_get_contents()" function with something that works with local storage but also with remote storage. Also, I'll change the way the file paths are constructed, to accomodate the remote storage situation. I'll post again here when finished.

titanium

2025-05-29 17:39

reporter   ~0000132

Ok, thank you!

DoubleBastionAdmin

2025-06-02 20:31

administrator   ~0000133

I have just published Pax Fax version 1.2.0, which addresses all the problems discussed above. When you have the time please test it.

titanium

2025-06-03 08:05

reporter   ~0000134

Hi there. Great, thank you!
I just tested it and the file upload (and file choice from nextcloud) as well as fax sending seem to work great now.

I will ask the team member to test it as well, to see if he runs into any problems.

And then we will also test potentially receiving faxes to see if that works well too.
I'll keep you posted.

Thanks again.

titanium

2025-06-06 02:24

reporter   ~0000135

Hi, the team member was able to send faxes as well now, so all good.
They wont be having a need to receive faxes for the near future, so we wont be testing that for now.

Thank you again for your help with making this work.

DoubleBastionAdmin

2025-06-06 05:33

administrator   ~0000136

When you have the time, please consider sending a fax to your own number to confirm if you can receive faxes also. It's possible that you will want to receive faxes in the future. If you send a fax to your own number the file is actually sent to Sinch and Sinch treats it as a regular fax sent by a regular sender. After processing it, Sinch sends it to Pax Fax, so, you should receive it like any other fax.

If you have already entered the callback URL in your Sinch account (as instructed on the app's settings page, under "Sinch callback URL"), all you have to do is to choose your number in the "Set ID" field, then enter the same number in the destination box, then choose the file you want to send and click Send. Then, in about one minute, you should see a Nextcloud notification about a recently received fax and if you click the "Received faxes" button you should see the received fax as a pdf file.

You can also send a free fax to your fax number from a service like gotfreefax.com .

titanium

2025-06-06 06:25

reporter   ~0000137

Hi, we don't have an available ID in the set ID field, because we haven't purchased a phone number on Sinch. As such, we can't receive faxes without paying for purchasing a phone number.

DoubleBastionAdmin

2025-06-06 09:27

administrator   ~0000138

Ok, I see.
Yet, after spending the $2 of your trial account you will need a fax number to send and receive faxes.
I find Sinch more convenient than Phaxio because to rent a fax number from Sinch costs around $0.9 per month for an American/Canadian number, whereas with Phaxio, the same number would cost $2 per month. This is the only ongoing monthly cost. It will cost more only if you actually send or receive faxes. In USA and Canada it's $0.045 per sent or received page (as opposed to Phaxio where it's $0.07 per sent/received page).

titanium

2025-06-06 10:08

reporter   ~0000139

Yeah the costs are nice with Sinch. I will follow up with the team - they will likely want to upgrade and add a phone number after they test this in real world application with the trial balance.

Issue History

Date Modified Username Field Change
2025-04-05 07:33 titanium New Issue
2025-04-05 10:02 DoubleBastionAdmin Note Added: 0000101
2025-04-06 03:03 titanium Note Added: 0000102
2025-04-06 13:04 DoubleBastionAdmin Note Added: 0000103
2025-04-06 14:07 titanium Note Added: 0000104
2025-04-25 06:52 DoubleBastionAdmin Note Added: 0000105
2025-04-25 06:55 DoubleBastionAdmin Note Edited: 0000105
2025-04-29 05:05 titanium Note Added: 0000106
2025-05-17 08:23 DoubleBastionAdmin Note Added: 0000111
2025-05-18 16:11 titanium Note Added: 0000112
2025-05-29 05:54 titanium Note Added: 0000113
2025-05-29 06:28 titanium Note Added: 0000114
2025-05-29 09:23 DoubleBastionAdmin Note Added: 0000115
2025-05-29 09:32 DoubleBastionAdmin Note Added: 0000116
2025-05-29 12:22 titanium Note Added: 0000117
2025-05-29 12:26 titanium Note Added: 0000118
2025-05-29 12:28 titanium Note Added: 0000119
2025-05-29 14:13 DoubleBastionAdmin Note Added: 0000120
2025-05-29 14:23 DoubleBastionAdmin Note Added: 0000121
2025-05-29 14:29 titanium Note Added: 0000122
2025-05-29 14:31 titanium Note Added: 0000123
2025-05-29 15:07 DoubleBastionAdmin Note Added: 0000124
2025-05-29 15:24 DoubleBastionAdmin Note Added: 0000125
2025-05-29 15:37 titanium Note Added: 0000126
2025-05-29 15:43 titanium Note Added: 0000127
2025-05-29 15:51 titanium Note Added: 0000128
2025-05-29 16:01 DoubleBastionAdmin Note Added: 0000129
2025-05-29 17:00 titanium Note Added: 0000130
2025-05-29 17:32 DoubleBastionAdmin Note Added: 0000131
2025-05-29 17:39 titanium Note Added: 0000132
2025-06-02 20:31 DoubleBastionAdmin Note Added: 0000133
2025-06-03 08:05 titanium Note Added: 0000134
2025-06-06 02:24 titanium Note Added: 0000135
2025-06-06 05:33 DoubleBastionAdmin Note Added: 0000136
2025-06-06 06:25 titanium Note Added: 0000137
2025-06-06 09:27 DoubleBastionAdmin Note Added: 0000138
2025-06-06 10:08 titanium Note Added: 0000139