Product Updates & Casual Natively Discussion

shitsurei · January 9, 2026, 1:31am

DMed you.

shitsurei · January 9, 2026, 1:34am

fwiw, it seems to be working (if a tad slow) for me now. Looks like the episodes populating issue was also fixed too Thank you!!

Naphthalene · January 9, 2026, 1:39am

Well, I just got “Internal Server Error”, so it’s not the case for me

brandon · January 9, 2026, 1:39am

Ok, identified the issue, pushing out a fix now. Currently only item pages & item search are broken. Was related to the way i fixed the previous server issue.

Edit: I’m sorry y’all, still running into issues. Will keep you updated.

brandon · January 9, 2026, 2:40am

Ok! It’s all fixed! What a dumb, dumb issue…

Edit: For those intrigued..

Tech Details

Natively has duplicate servers for protection on many things but one server, our caching server for quick data retrieval (redis), went down this morning. That took everything down. As i said before, I’m pretty sure it went down because it was overloaded by backfilling… something to address… but a simple reboot fixed that server, no problem.

What took the next hour or so was figuring out why the other servers were still going bonkers. Apparently I hardcoded that redis server address in a few places and when you reboot the address changes. So I had to go through and fix those spots. One of the spots is on our NextJs page renderer on the item pages and apparently that needs modules stored in the redis system to work. Realizing what modules were turned off by the reboot and figuring out that system is what lasted the next hour

Apologies on the outage! And in general, the flakiness the past week! Will try to address.

Naphthalene · January 9, 2026, 12:09pm

Just in case it’s relevant, I just got the “issue with our server” error when trying to add a book just now.

eefara · January 9, 2026, 1:08pm

Thanks for the update and all the fixes, brandon!

earwen · January 9, 2026, 2:53pm

Found a very strange bug. I was trying to search for currently airing show, 「お前ごときが魔王に勝てると思うな」と勇者パーティを追放されたので、王都で気ままに暮らしたい. I select video on the header bar, start typing “omae” and the header completely dissappears. I tried it with other words but regardless of whether there are results or not, I can’t replicate this bug besides for this show.
I mean this whole section dissappears, not just the search bad. I can only bring it back by refreshing.

mic · January 9, 2026, 3:17pm

The series page looks strange: 「お前ごときが魔王に勝てると思うな」と勇者パーティを追放されたので、王都で気ままに暮らしたい S1 | L30??. That may be related. Maybe pressing the synch button will fix it, though.

暁のルナ · January 9, 2026, 4:45pm

Also happens to me - Windows 11, Chrome. Console output:

core.f488d7352bda.js:1 TypeError: Cannot read properties of null (reading 'url')
    at m (core.f488d7352bda.js:163:66535)
    at gi (core.f488d7352bda.js:73:59624)
    at Ds (core.f488d7352bda.js:73:104551)
    at jl (core.f488d7352bda.js:73:90414)
    at Nl (core.f488d7352bda.js:73:90339)
    at Sl (core.f488d7352bda.js:73:87679)
    at core.f488d7352bda.js:73:46029
    at n.unstable_runWithPriority (core.f488d7352bda.js:163:3472)
    at Qo (core.f488d7352bda.js:73:45738)
    at ta (core.f488d7352bda.js:73:45974)
    at ea (core.f488d7352bda.js:73:45909)
    at bl (core.f488d7352bda.js:73:84445)
    at ji (core.f488d7352bda.js:73:63281)
    at z (core.f488d7352bda.js:163:67867)
    at Object.<anonymous> (core.f488d7352bda.js:163:67029)
    at l (core.f488d7352bda.js:24:25096)
    at Object.fireWith [as resolveWith] (core.f488d7352bda.js:24:25844)
    at T (core.f488d7352bda.js:24:77399)
    at XMLHttpRequest.<anonymous> (core.f488d7352bda.js:24:79867)
    at XMLHttpRequest.i (core.f488d7352bda.js:1:54770)
    at XMLHttpRequest.nrWrapper ((index):37:14077)
(anonymous) @ core.f488d7352bda.js:1

(index):37 Uncaught TypeError: Cannot read properties of null (reading 'url')
    at m (core.f488d7352bda.js:163:66535)
    at gi (core.f488d7352bda.js:73:59624)
    at Ds (core.f488d7352bda.js:73:104551)
    at jl (core.f488d7352bda.js:73:90414)
    at Nl (core.f488d7352bda.js:73:90339)
    at Sl (core.f488d7352bda.js:73:87679)
    at core.f488d7352bda.js:73:46029
    at n.unstable_runWithPriority (core.f488d7352bda.js:163:3472)
    at Qo (core.f488d7352bda.js:73:45738)
    at ta (core.f488d7352bda.js:73:45974)
    at ea (core.f488d7352bda.js:73:45909)
    at bl (core.f488d7352bda.js:73:84445)
    at ji (core.f488d7352bda.js:73:63281)
    at z (core.f488d7352bda.js:163:67867)
    at Object.<anonymous> (core.f488d7352bda.js:163:67029)
    at l (core.f488d7352bda.js:24:25096)
    at Object.fireWith [as resolveWith] (core.f488d7352bda.js:24:25844)
    at T (core.f488d7352bda.js:24:77399)
    at XMLHttpRequest.<anonymous> (core.f488d7352bda.js:24:79867)
    at XMLHttpRequest.i (core.f488d7352bda.js:1:54770)
    at XMLHttpRequest.nrWrapper ((index):37:14077)
envelope/?sentry_key=00782e3def4140dc84e6cd7cad6851ed&sentry_version=7&sentry_client=sentry.javascr…:1  POST https://o364332.ingest.sentry.io/api/4720961/envelope/?sentry_key=00782e3def4140dc84e6cd7cad6851ed&sentry_version=7&sentry_client=sentry.javascript.browser%2F7.56.0 429 (Too Many Requests)

araigoshi · January 9, 2026, 7:48pm

Firefox has a little bit more information in the error output:

TypeError: can't access property "url", t.image is null
    m https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    gi https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    Ds https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    jl https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    Nl https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    Sl https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    ta https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    unstable_runWithPriority https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    Qo https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    ta https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    ea https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    bl https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    ji https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    z https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    g https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    l https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:24
    fireWith https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:24
    T https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:24
    n https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:24
    i https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    nrWrapper https://learnnatively.com/:37
    inPlace https://learnnatively.com/:37
    b https://learnnatively.com/:37
    i https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    nrWrapper https://learnnatively.com/:37
    nrWrapper https://learnnatively.com/:37
    c https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    h https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    n https://learnnatively.com/:37
    XMLHttpRequest https://learnnatively.com/:37
    XMLHttpRequest https://learnnatively.com/:37
    xhr https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:24
    send https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:24
    ajax https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:24
    g https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    _ https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    u https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    g https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    l https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    i https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    nrWrapper https://learnnatively.com/:37
    setTimeout handler*nrWrapper https://learnnatively.com/:37
    s https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    l https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    i https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    nrWrapper https://learnnatively.com/:37
    setTimeout handler*nrWrapper https://learnnatively.com/:37
    s https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    l https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    i https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    nrWrapper https://learnnatively.com/:37
    setTimeout handler*nrWrapper https://learnnatively.com/:37
    s https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    l https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    i https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    nrWrapper https://learnnatively.com/:37
    setTimeout handler*nrWrapper https://learnnatively.com/:37
    s https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:1
    u https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    E https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    G https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    onChange https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:163
    m https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    E https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    T https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    T https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    O https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    C https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    R https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73
    xn https://d1sbtzet6n43nd.cloudfront.net/js/core.f488d7352bda.js:73

And yeah, if you load the season page, there’s no image:

読み蛙 · January 10, 2026, 9:57am

I’m also getting an Issues with our servers when adding a book

Book I'm trying to add, if it's any help

( https://www.amazon.co.jp/男尊女子-集英社文庫-酒井-順子/dp/4087441121/356-3889156-0352745?pd_rd_w=1rNoA&content-id=amzn1.sym.a4dc92d7-7100-437e-b3e3-2349e8298523&pf_rd_p=a4dc92d7-7100-437e-b3e3-2349e8298523&pf_rd_r=FY0H5DFT2FMA1SP1YS2Z&pd_rd_wg=5OO9u&pd_rd_r=319a9c9e-6add-42e6-a433-8dd56ee26349&pd_rd_i=4087441121&psc=1 )

earwen · January 10, 2026, 12:42pm

I wonder if it would be useful to have a minor bugs thread since we always report here. This thread seems ostensibly about updates.

Anyway I also wanted to report chainsaw man is missing images for 2 volumes despite syncs

brandon · January 10, 2026, 9:24pm

Forum Announcement

I’d like to welcome our first Forum moderators, @eefara @Naphthalene @monace @mitrac! Each of them have been wonderful members of the community and they have graciously volunteered to help out a bit as moderators. If you ever need the attention of a moderator, simply include @moderators in your message.

In addition, @eefara and @Naphthalene have been granted admin privileges as well.

Welcome!

(somewhat) Private Study Log Category

Many people expressed that they’d prefer their personal study logs to only be available to logged in users and not to search engines. You can now achieve this by placing your study logs in the Study Logs (Private) category.

Natively Looking For Technical Partners

Please look here for more information! I’ve already received a number of interested requests, so the search is starting to pickup steam

And duly noted everyone (@earwen @Naphthalene @読み蛙) about that book upload issue! That’s my priority number one, hopefully fixed tomorrow. I appreciate everyone’s support as I ramp back up on dev work

seanblue · January 11, 2026, 2:01am

Oh, I got a weird one. Typing “ps” into the video search bar (not the book search bar) makes the entire top menu bar disappear. I was just trying to look up “psycho pass”.

暁のルナ · January 11, 2026, 2:15am

“Issues with our servers” when trying to add the following manga: Amazon.co.jp: 私たちは付き合ってない。 (百合コレ) eBook : ドスコイ: Kindle Store

Everything works until tapping the Create Book btn

shitsurei · January 11, 2026, 2:39am

I feel like earwen had a similar bug earlier this week?

brandon · January 11, 2026, 11:09am

Ok! @暁のルナ @earwen @Naphthalene @読み蛙 I think I fixed the book upload bug!!

It was actually quite easy and not an issue with amazon thankfully.

Tech Details

So Amazon book titles have a lot of nonsense around them we we don’t want to show. In order to clean the titles, we go through all the books in our database and compare the raw amazon title stored with the current Natively title and use the difference between those to make a pattern on what to remove. We store all those patterns in a cache (because generating those patterns takes a while). However, the book upload process needs this cache otherwise it crashes out and with all the recent server issues, the update mechanism wasn’t run on time and the cache disappeared.

The upload process definitely shouldn’t crash if that cache isn’t there.. so that’s something I need to fix pronto, yikes haha.

Really sorry for that bug, I know that was a big one. I’ll try to find people who were hitting issues and ping them directly.

Naphthalene · January 11, 2026, 11:17am

It worked!

暁のルナ · January 11, 2026, 11:19am

I was able to add the book now, thx for the fix & explanation