
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
1 person marked this as a favorite. |

Chiming in that I've been using this tool forever and absolutely appreciate everything that everyone volunteers to do; would be happy to voluntarily subscribe to something like a Patreon just to offset costs.
Also reporting data: I don't see the PF2E Beginner Box or Menace Under Otari listed anywhere, since it probably gets overlooked as a path to PFS credit.

![]() ![]() ![]() ![]() ![]() ![]() |

There are a number of scenarios missing right now.
Unfortunately, the internet being what it is, someone started trying to hack the admin panel for the database.[Editing in some corrections] External database access was disabled. Then it was necessary to upgrade the server, and that broke some things.
We'll get back to it once we get access.

![]() ![]() ![]() ![]() ![]() ![]() |

Unfortunately it's a two-fold problem. The filters are hard-coded, so new seasons require code maintenance. And the database has been locked down for awhile, so those of us who were helping maintain the data can't make updates.
Maglok has other priorities these days and has generously kept this going far beyond his involvement in PFS. We're looking for options to keep it going but I'd need to find someone who can maintain the code.

![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
4 people marked this as a favorite. |

For those interested: since Maglok is basically no longer involved in PFS, he's been looking to transfer the PFStracker project to someone else. I'm currently building a v2.0 in a tech stack I'm more comfortable maintaining (Laravel), that will also make it easier for us to add new scenario seasons and all that good stuff.
There's still some work to be done before it's ready but I'm making good progress.

![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
2 people marked this as a favorite. |

Are we going to be able to transfer profiles?
Yeah, I've been working on porting the database so all your play history will be there.
Because Maglok followed proper security practices, I won't be able to copy over the passwords to the new database, so everyone will have to do a "I forgot my password" reset.

![]() ![]() ![]() ![]() ![]() ![]() ![]() |

Davor Firetusk wrote:Because Maglok followed proper security practices, I won't be able to copy over the passwords to the new database, so everyone will have to do a "I forgot my password" reset.Absolutely worth the cost of entry. Speaking of costs, any way we can help with that sort of problem and/or volunteer for bulk data entry?

![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |

It's there, there's just a problem with chrome not acknowledging the SSL cert.
Loads fine in Firefox and Qualys confirms the cert is valid. Source
You can disable safeties in chrome to access it, use a different browser or wait for Google to fix.

![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |

Hey folks :)
As far as I can tell the SSL setup is quite run of the mill Letsencrypt/Certbot, and I can't find any problems with it. I suspect the Chrome complaints are based on a caching issue that will hopefully fade.
As for email, the main difficulties seem to be:
* People who used to use a different email address, that they no longer have access to.
* Yahoo doesn't like my DNS settings for email somehow. I fixed some settings that were initially incomplete but I still get the occasional rejection. Apparently Yahoo is particularly difficult about these things.
In either case, it's easy enough for me to fix it for people manually. The contact link at the bottom of the page is a good way to get my attention :)
I don't really need financial help with this, costs are pretty modest. If someone knows a lot about debugging Yahoo's issues with DMARC/SPF/DKIM though, I could use help with that.

![]() |

As far as I can tell the SSL setup is quite run of the mill Letsencrypt/Certbot, and I can't find any problems with it. I suspect the Chrome complaints are based on a caching issue that will hopefully fade.
What I observe is that chrome is getting the old cert for https://www.pfstracker.net (the www. subdomain).
Whereas if you just go to the naked domain https://pfstracker.net, etc you get the correct new cert.
This shouldn't really matter, but it might explain some folks' experience and without a successful redirect they may sometimes give up early (?)

![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
1 person marked this as a favorite. |

Ascalaphus wrote:As far as I can tell the SSL setup is quite run of the mill Letsencrypt/Certbot, and I can't find any problems with it. I suspect the Chrome complaints are based on a caching issue that will hopefully fade.What I observe is that chrome is getting the old cert for https://www.pfstracker.net (the www. subdomain).
Whereas if you just go to the naked domain https://pfstracker.net, etc you get the correct new cert.
This shouldn't really matter, but it might explain some folks' experience and without a successful redirect they may sometimes give up early (?)
Ah! Thank you! That's what I was overlooking. Should be better now.